[ci] extend backport workflow to work with arbitrary branches #6108
+59
−38
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
Expands the PR backport workflow so maintainers can target any release branch using labels, instead of being limited to the
core/x.y
release lines. The workflow now collects labels formatted as plain version numbers (1.24
) as before, plus new prefixes likebranch:release/hotfix
orbackport:partner/foo
, validates that each referenced branch exists, and then cherry-picks the source merge commit to every target.All generated PRs and failure comments reference the actual branch name, making it clear where the backport landed or why it failed. This keeps the existing opt-in flow (
needs-backport
) but makes it flexible enough for custom support and partner branches without extra manual work.┆Issue is synchronized with this Notion page by Unito