Repository navigation
fix: mark auto-tag tags explicitly for the release guard - #285
Merged
Merged
Conversation
auto-tag now adds an "[auto-tag]" marker to the tag message and the release.yml guard checks for it, so the two workflows no longer depend on the git user.name string alone. The tagger check remains as a fallback for tags created before the marker. Claude-Session: https://claude.ai/code/session_01Y29fBeRP344FME6de48wUv
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 14 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Oct 14, 2026
Merged
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.
Closes #282
#279 で追加した guard は、tagger 名が
github-actions[bot]かどうかの文字列比較だけで auto-tag のタグを判定していました。そのため、auto-tag.ymlの git の設定を変えるだけで判定が効かなくなり、#278 の問題が再発するおそれがありました。変更内容
auto-tag.yml: タグのメッセージに目印[auto-tag]を入れるようにしました（Release vX.Y.Z [auto-tag]）。同期が必要なことをコメントで残しています。release.yml: guard ジョブで、タグのメッセージに[auto-tag]が含まれていればスキップします。tagger がgithub-actions[bot]かどうかの判定は、目印を入れる前に作られたタグのために残しました。2 つのワークフローの約束事が、目に見える目印として残るようになります。
動作の確認について
タグのメッセージはリリース本文の生成には使っていないので、目印が入ってもリリースノートは変わりません。ワークフロー上での動作は、次のリリースで確認することになります。
https://claude.ai/code/session_01Y29fBeRP344FME6de48wUv