ci: don't run CI on draft PRs #7518
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alvicsam
added
the
R0-silent
alvicsam
changed the title
AndWeHaveAPlan
approved these changes
Feb 10, 2025
|
A lot of times I actually create draft PRs specifically to run CI. |
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR adjusts gtihub workflow so they don't run on draft PRs. There was also an idea to trigger CI in a draft state using label but after experiments I decided not to implement it. The main reason is that any label change will trigger workflows.
close https://github.com/paritytech/ci_cd/issues/1099
close #7168