bpo-44972: Add workflow_dispatch trigger to GitHub Actions workflows #27873
Conversation
|
Please rebase your PR. |
nightlark
force-pushed
the
gha-workflow_dispatch-trigger
branch
from
88a1808
to
f1165b1
|
PR is rebased. |
|
Probably didn't need to be rebased, and now it's likely to fail until you merge in the current main (which has another, unrelated CI fix). We squash merge at the end anyway, so provided there are no conflicts, there'll only be one commit (and we'll edit the message for consistency). |
|
Okay, I merged in the current main. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Adds
workflow_dispatchtriggers to run GHA workflows in development branches of forks (runs in context of the fork, using runner pool of the account with the fork).To be able to trigger a CI build for a branch the workflow yaml files in that branch needs the
workflow_dispatchtrigger, so having the trigger added in the main/3.x branches should make so jobs can be manually triggered for all new branches created or rebased. If themain/defaultbranch doesn't haveworkflow_dispatchadded, theRun Workflowdrop down menu doesn't show up.https://bugs.python.org/issue44972
The text was updated successfully, but these errors were encountered: