docs(contributing): drop --branch next/major from clone snippet; clarify PR target#3198
Merged
Merged
Conversation
…ify PR target The recommended clone command pinned `--branch next/major`, which left contributors landing on a long-lived feature branch instead of `master` (the actual default branch and PR target). I tripped on this myself and opened #3196 against `next/major` before noticing every other open PR targets `master`. Drop the `--branch next/major` flag so a fresh clone lands on the default, and add a short note explaining that `master` is the PR target while `next/major` is reserved for the next major release.
dr-bonez
requested changes
Apr 30, 2026
Contributor
Author
|
Applied verbatim and pushed. Thanks @dr-bonez — adopted your wording verbatim in |
dr-bonez
approved these changes
May 1, 2026
Contributor
Author
|
Thanks @dr-bonez! |
Adopt the maintainer-authored explanation of the branch-targeting
policy verbatim: master tracks the current release (and during a
beta.X pre-release, PRs for new features and bugfixes land there),
with next/{patch,minor,major} holding work waiting for the
corresponding future release.
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
2 participants
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.
Why
The "Cloning the Repository" snippet in CONTRIBUTING.md tells you to clone with
--branch next/major:…but
masteris the actual default branch and the PR target. I tripped on this myself and opened #3196 againstnext/majorbefore noticing every other recent PR (#3190…#3197) targetsmaster. Easy mistake to make from the doc as written.What
--branch next/majorflag from the clone command so a fresh checkout lands on the default branch.masteris the PR target andnext/majoris the long-lived branch for the next major release (only target it for changes that must wait for that bump).No build / behaviour changes — docs only.