chore: trigger CI jobs on all release-related branches #29274
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
Currently, we trigger the bulk of our CI on all PRs, and on push to the `master` and release branches. Release branches currently are defined as `[0-9].[0-9]` meaning it will work for `3.5` and `10.10`, but not for `3.1.1`, `3.0-beta2` or whatever other release branch that don't fit the "minor" release pattern. Not I'm extending this to `[0-9].[0-9]*`. As a glob that mean it'll run for practically anything that loosely looks like a release branch. The goal is to make it easier for people working in forks, whether private or public to trigger CI while doing their own release management. Currently if you want to trigger CI, you pretty much to either open a dummy PR, or push to a branch that fits the current pattern, which doesn't allow for flexibility around branch naming, which is key for release management. This PR should not affect the repo or release process on this repo, it's just about making it easier to trigger CI on forks.
mistercrunch
requested review from
villebro,
geido,
eschutho,
rusackas,
betodealmeida,
nytai,
craig-rueda,
john-bodley,
kgabryje and
dpgaspar
as code owners
github-actions
bot
added
the
github_actions
john-bodley
added
the
review:checkpoint
michael-s-molina
approved these changes
Jun 17, 2024
rusackas
approved these changes
Jun 17, 2024
michael-s-molina
removed
the
review:checkpoint
eschutho
pushed a commit
that referenced
this pull request
Jul 24, 2024
mistercrunch
added
🏷️ bot
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.
SUMMARY
Currently, we trigger the bulk of our CI on all PRs, and on push to the
masterand release branches.Release branches currently are defined as
[0-9].[0-9]meaning it will work for3.5and10.10, but not for3.1.1,3.0-beta2or whatever other release branch that don't fit the "minor" release pattern.Not I'm extending this to
[0-9].[0-9]*. As a glob that mean it'll run for practically anything that loosely looks like a release branch.The goal is to make it easier for people working in forks, whether private or public to trigger CI while doing their own release management. Currently if you want to trigger CI, you pretty much to either open a dummy PR, or push to a branch that fits the current pattern, which doesn't allow for flexibility around branch naming, which is key for release management.
This PR should not affect the repo or release process on this repo, it's just about making it easier to trigger CI on forks.