In theory changing the event to pull_request_target: [labeled], adding if: github.event.label.name == 'start-ci' to the job and changing every use of github.event.issue.number with github.event.number should be enough for this use case, with the caveat that existing PRs need to be rebased for the action to trigger (because of nodejs/node#34707 (comment)). If that caveat doesn't work for this repo, the schedule approach we use on core also works, but requires more changes (happy to help anyone who wants to work on it).

Makes sense to me. I think that if the preview is successful, it could also remove the label.

The instructions in https://github.com/nodejs/nodejs.dev/blame/695b54d12f249028b6120a2e7734fa6729e1e6b9/.github/PULL_REQUEST_TEMPLATE.md#L18 will also need to update if this is switched

The job I referenced on core removes the label as soon as it is kicked off. I think there is an additional label added if it fails I would imagine that pattern would be worth following

If we switch to labels does that mean only members can start the ci and create a preview link?

Yes

but folks with a triage role could kick it off as well

Could be worth updating the PR template with a checkbox like this, if only so that triagers/maintainers know without having to specifically be asked:

• This should be preview deployed

As a bonus, the action could also auto-add the label if that is checked - though it wouldn't trigger the next workflow (because Actions can't trigger Actions), but we could add it to the same pull_request.opened workflow.

though it wouldn't trigger the next workflow (because Actions can't trigger Actions)

It works if you use a personal token (we can create one for @nodejs-github-bot and add it to the repo)

Took a try with #851

Potentially, the label could be added to PULL_REQUEST_TEMPLATE frontmatter if a preview is wanted on all PRs