workflows: auto-create patch release tracking issue on /backport - #4046
Merged
rickeylev merged 1 commit intoAug 14, 2026
Merged
Conversation
Allow commenting `/backport` on a pending PR to automatically create a patch release tracking issue if no active release tracking issue exists. Refactor release template loading into a reusable helper and update add-backports to use GitHub Actions workflow notice/error formatting.
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.
Previously, commenting
/backporton a PR failed if no release trackingissue was open, requiring maintainers to manually create one first.
When auto-discovering tracking issues finds no open release issue,
automatically create a new patch release tracking issue for the next
patch version and add the requested backports to it.
Also centralize release tracking template loading and RC task stripping
for patch releases into a shared helper function, prevent RC tasks from
being added to patch release tracking issues, and format workflow log
messages with GitHub Actions annotations.