docs: document staging-rc tag naming convention#72
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
WalkthroughUpdates documentation in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Pull request overview
Updates internal repo documentation to clarify how staging deployments are triggered via Git tag pushes, helping contributors follow the intended release/deploy workflow.
Changes:
- Document that staging deploys are triggered by tags matching
v*-staging* - Add an explicit recommended staging tag naming convention
v<version>-staging-rc-<N>with examples
Acknowledge legacy tag formats while recommending staging-rc-N. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
v<version>-staging-rc-<N>tag naming convention in.claude/claude.mdunder Releases & VersioningTest plan
.claude/claude.mdrenders correctly on GitHub🤖 Generated with Claude Code