Open
Conversation
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.
Summary
Adds a CONTRIBUTING.md at the repo root explaining how technical authors should work with the two active branches now that v20 maintenance and v21 development run in parallel.
Covers three scenarios: v20-specific fix, fix relevant to both versions, v21-only content. Aimed at authors who know basic git (branch, commit, PR) but haven't worked with multiple base branches before — shows both GitHub-UI and CLI workflows, with a quick-reference table and common mistakes.
Follow-up
After merge, cherry-pick to `v20.0` so the file exists on both branches (same pattern as the Full Release workflow). Happy to do that in a follow-up PR.