ci: auto-label release PRs with release-management#14744
Open
ci: auto-label release PRs with release-management#14744
Conversation
Tags every PR opened by release-1-create-pr.yml and release-3-master-into-dev.yml (release, master-into-dev, master-into-bugfix) with the release-management label, so release PRs are easy to filter and automate on without title/branch-regex matching. Co-Authored-By: Claude Opus 4.7 (1M context) <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
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
Create Pull Requeststeps in.github/workflows/release-1-create-pr.ymland.github/workflows/release-3-master-into-dev.ymltoawaitgithub.rest.pulls.create(...)and immediately callgithub.rest.issues.addLabels(...)with['release-management']..github/labeler.yml, so the label isn't subject tosync-labels: truere-evaluation on later PR events.Prerequisite
The
release-managementlabel must exist in the repo before the next release workflow runs —issues.addLabelsdoes not create missing labels. Create it once via the Labels UI or:Test plan
release-managementlabel exists in the repo.release-managementlabel and theCreate Pull Requeststep is green in the Actions log.…into devand…into bugfixPRs should get the label.🤖 Generated with Claude Code