docs(contributing): make CONTRIBUTING.md SSOT for branching workflow#158
Open
labradorite-dev wants to merge 1 commit into
Open
Conversation
Clarify that feature branches should target `beta`, not `main`. Collapse duplicated setup and release notes in README.md and AGENTS.md into references back to CONTRIBUTING.md.
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.
betavs.mainbranchingBackground
Received a comment on #155 that I should have branched off
betabut that branching workflow wasn't immediately clear to me from docs. This further clarifies (based on GH PR history) the branching workflow and also collapses to a single source of truth.Description
Documentation changes.
Acceptance Criteria
Does this documentation match the maintainer understanding of the branching workflow?