ci: run CI and release workflows on release branches - #1774
Merged
Merged
Conversation
ci.yml and release.yml only matched main, so PRs to and merges into branch-* release branches ran no build or tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Which issue does this PR close?
Closes #1773.
Rationale for this change
PRs targeting release branches (e.g.
branch-54) currently get no build or test CI, and merges into them never run the release build.ci.ymlonly triggers onpull_requesttomainandrelease.ymlonly onpushtomain(plus tags), so the only workflow that runs on a release branch is RAT. #1772 merged intobranch-54without any build or tests running.What changes are included in this PR?
ci.yml: also trigger onpull_requesttargetingbranch-*.release.yml: also trigger onpushtobranch-*.GitHub reads workflow definitions from the branch the event occurs on, so this change is also backported to
branch-54in a separate PR. Landing it onmainmeans futurebranch-NNrelease branches inherit it.Are there any user-facing changes?
No. CI only.
🤖 Generated with Claude Code