chore: document master/dev/next branch model + wire CI triggers - #709
Merged
Conversation
Adopt the git-flow release model (master=patch/publish, dev=minor, next=major; dev/next merge into master to ship). Only master publishes. - CLAUDE.md: add Branch Model table + promotion rules under Releasing - docs/contributing: Branch Model section, base-branch guidance in Before Submitting and Branch Naming - pr-checks.yml, changeset-reminder.yml: run on PRs into dev/next too - release.yml: comment that master-only publish is intentional - add .github/PULL_REQUEST_TEMPLATE.md with a base-branch checklist
Base-branch guidance lives in CLAUDE.md + contributing; a template form adds friction without reliably being filled in.
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.
Adopts the git-flow release model and documents it. Companion to the PR base-branch audit (routed 13 feature PRs to
dev, kept fixes onmaster).Model
master= patch/fix + publish ·dev= features (minor) ·next= breaking (major). Onlymasterpublishes via changesets;dev/nextaccumulate work and merge intomasterat the next minor/major cut.Changes
## Releasing.### Branch Modelsection; base-branch guidance in Before Submitting and Branch Naming.dev/nexttoo (weremaster-only), so feature/breaking PRs get CI + the changeset nudge.master-only by design (no trigger change)..changeset/config.jsonbaseBranch: masterleft unchanged — correct under this model (master is the release base).Notes
codecov-healthgate in pr-checks staysmaster-only (coverage badge tracks the released branch).