docs: adopt GitFlow with milestone-versioned release branches - #20
Merged
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.
Formalizes the branching/release policy in CLAUDE.md (Git conventions + Definition of Done):
mainholds only released, tagged code.release/vX.Y.Z— one per GitHub milestone; milestone work integrates here, not onmain. The branch carries that milestone's version.feature/<name>branches off the release branch and PRs back into it.develop/nextbranch — release branches are milestone-versioned.vX.Y.Zonly when the release branch merges tomain.DoD updated: branch-correctly first, version = milestone version, tag only on release→main merge.