docs: write down branch and release conventions - #61
Merged
Conversation
CLAUDE.md carried one line on versioning ("changesets; pnpm release") and
nothing on branches. The repo had drifted to 18 remote branches across six
naming conventions and four unreleased changesets, with D53 merged but
unpublished across three decisions.
Records the rules that were already implicit, plus four traps this repo has
actually hit:
- squash-merge makes `git branch --merged` useless; use `git cherry`
- `gh pr merge --auto` exits 0 without arming auto-merge
- `changeset tag` creates tags but never pushes them
- `pnpm vr` cannot pass outside CI, and a local run writes junk baselines
Also bumps the decision-log range to D56 and warns to check the highest
number in use first — two parallel sessions collided on D54/D55.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Docs only — no source, no changeset (nothing consumer-visible ships).
CLAUDE.mdhad one line on versioning and nothing on branches, so there was no rule for which of six naming conventions to reach for. The repo had drifted to 18 remote branches — all merged — and four unreleased changesets, which is how D53 stayed merged-but-unpublished across three decisions.What's recorded
The conventions that were already implicit (branch naming, one-branch-one-PR, changeset per change, cut a release when the queue is non-empty), plus four traps this repo has actually hit and that cost real time to rediscover:
git branch --mergedmainby hash. Usegit cherry -v main <branch>.gh pr merge --autochangeset tagpnpm vr-darwin.pngbaselines.Also bumps the decision-log range from D42 to D56, and adds a warning to check the highest number in use before claiming the next — two parallel sessions collided on D54/D55 this week.
🤖 Generated with Claude Code