Skip to content

docs: document staging-rc tag naming convention#72

Merged
FSM1 merged 2 commits into
mainfrom
docs/staging-rc-tag-convention
Feb 9, 2026
Merged

docs: document staging-rc tag naming convention#72
FSM1 merged 2 commits into
mainfrom
docs/staging-rc-tag-convention

Conversation

@FSM1

@FSM1 FSM1 commented Feb 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • Documents the v<version>-staging-rc-<N> tag naming convention in .claude/claude.md under Releases & Versioning

Test plan

  • Verify .claude/claude.md renders correctly on GitHub

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings February 9, 2026 14:53
@coderabbitai

coderabbitai Bot commented Feb 9, 2026

Copy link
Copy Markdown

Walkthrough

Updates documentation in .claude/claude.md to replace the previous explanation of staging deployment tagging behavior with a new rule specifying that staging deploys are triggered by v*-staging* tags and introduces a formal tagging convention: v-staging-rc-.

Changes

Cohort / File(s) Summary
Documentation Update
.claude/claude.md
Modified staging deployment tag documentation to specify that staging deploys are triggered by pushing tags matching the pattern v*-staging* and introduced a concrete tag convention v-staging-rc- with sequential rc-N counter.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: documenting the staging-rc tag naming convention, which aligns with the file changes in .claude/claude.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/staging-rc-tag-convention

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment thread .claude/claude.md Outdated
Comment thread .claude/claude.md Outdated
Acknowledge legacy tag formats while recommending staging-rc-N.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@FSM1 FSM1 self-assigned this Feb 9, 2026
@FSM1 FSM1 merged commit 289c560 into main Feb 9, 2026
7 checks passed
@FSM1 FSM1 deleted the docs/staging-rc-tag-convention branch February 9, 2026 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants