ci: add dev- branches as supported PR target
#8828
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
michaelfig
approved these changes
Jan 26, 2024
mhofman
added a commit
that referenced
this pull request
Jan 30, 2024
mhofman
added a commit
that referenced
this pull request
Jan 30, 2024
mhofman
added a commit
that referenced
this pull request
Jan 30, 2024
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.
refs: #8578
Description
This treats the
dev-*branches likerelease-*branches, and runs CI on those branches, including publishing NPM and docker images (needed for stages release work), and will trigger integration checks when a label is applied for a PR targeting those branches. We still don't have mergify integration on these branches, but that will come in a future PR.Security Considerations
None
Scaling Considerations
None
Documentation Considerations
Will update all wiki pages as necessary later
Testing Considerations
Will check triggers once this PR merges
Upgrade Considerations
Will cherry-pick into release branch for good measure.