Promote dev to main: branching convention docs#3
Merged
Merged
Conversation
…#2) Companion to the new branch protection rules just applied to the repo: - main is release-grade, PR-only, linear history, no force-push/delete - dev is integration, accepts direct push but still no force/delete - feat/* is documented convention only; no GitHub-side rule — contributors push freely, rebase freely, PR to dev when done Adds a typical-loop snippet so contributors don't have to read GitHub settings to figure out the workflow. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Brings in PR #2 — CONTRIBUTING.md branching convention section. Docs only.