Don't run CI on update/* branches
#291
Merged
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
armanbilge
commented
Jun 5, 2022
| branches: ['**'] | ||
| branches: ['**', '!update/**'] |
There was a problem hiding this comment.
This took me aback at first, because I thought it meant it would not run CI for PRs from branches named update/**. But, no, it won't run CI for PRs targeting branches named update/**.
There was a problem hiding this comment.
Thanks for clarifying this. Can't imagine how many times people were confused with this. Maybe it's just an attempt to get more traffic to docs? 😆
This was referenced Jun 6, 2022
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.
See #177 (comment) for context.
Strategically named this branch
update/ignore-meto see if it works right.