Allow CI workflow to run on Pull requests, only when requested

[cpernot-hf]

Select Topic Area

Question

Body

Hi,

We would like to run CI on our PRs, only when the developer really wants it.

Is there a way to condition the whole workflow to not trigger, until this condition is met ?

We are currently trying to use a label RUN-CI on the PR, then the jobs needs to check if that label exists.
Here are the events in the workflow.

on:
  pull_request:
    types:
      - opened
      - synchronize
      - labeled

Here is a if condition example :

      (github.event.action == 'labeled' && github.event.label.name == 'RUN-CI') ||
      (contains(fromJSON('["synchronize", "opened"]'), github.event.action) && contains(github.event.pull_request.labels.*.name, 'RUN-CI')) }}

But this is annoying, because:

• the conditions are not easily readable
• it triggers a workflow for each event, even if there is no job to run
• if the last event action is 'labeled', but not a 'RUN-CI' label, the last workflow will be empty
• the status checks (and the favicon) in the PR discussion tab will display information about the last workflow, which is possibly not the one we want to use

We tried manual triggers (workflow_dispatch) but they are not attached to the PR status checks.

Solutions we could imagine :

• having a fake "hold/approval" job which would remove the need to listen to labeled events (this job should not use a real runner)
• having a if field on the workflow itself, which would avoid to trigger the unnecessary workflow

There is certainly other options that I can't see :)

Did I miss something ?

[spenserblack]

We would like to run CI on our PRs, only when the developer really wants it.

Would the "developer" be the contributor making the PR, or the repository maintainer(s) reviewing the PR?

If they're the contributor, perhaps you could use the draft status as a flag for when the workflow should run? You could use the ready_for_review event type.

[cpernot-hf]

We would like to run CI on our PRs, only when the developer really wants it.

Would the "developer" be the contributor making the PR, or the repository maintainer(s) reviewing the PR?

If they're the contributor, perhaps you could use the draft status as a flag for when the workflow should run? You could use the ready_for_review event type.

The "developer" is the contributor, but we want the CI to be green before the review process begins.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[cpernot-hf]

I still haven't found a working solution and I don't know which information I could share to help