Add auto-tagging workflow for release PR merges#53
Merged
Conversation
Manually creating and pushing tags after merging release PRs is error-prone and easy to forget. This workflow automates the process by extracting the version from the branch name (release-vX.Y.Z) and creating the corresponding tag, which then triggers the existing release pipeline. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dak2
force-pushed
the
add-release-tag-workflow
branch
from
3455665 to
7ce2ec0
Compare
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.
Summary
vX.Y.Ztag when arelease-vX.Y.Zbranch is merged into mainrelease.ymlworkflow, eliminating the manual tagging stepFlow
Test plan
release-v0.1.9automatically creates thev0.1.9tagrelease-vinvalid) fail validation🤖 Generated with Claude Code