Skip to content

docs: require explicit branch discipline - #1

Draft
bankkaroproduct wants to merge 1 commit into
mainfrom
agent/branch-discipline-cleanup
Draft

docs: require explicit branch discipline#1
bankkaroproduct wants to merge 1 commit into
mainfrom
agent/branch-discipline-cleanup

Conversation

@bankkaroproduct

Copy link
Copy Markdown
Owner

What changed

  • Requires every project template to declare its GitHub default branch, integration branch, and production deploy trigger.
  • Replaces generic main assumptions with project-specific branch-map language across setup, shipping, orchestration, hardening, handoff, review, and checkpoint docs.
  • Adds a safe existing-branch cleanup playbook: inventory first, classify keep/merge/park/delete, then delete remote branches only after review.

Why

APMs and agents should not have to guess which branch is the right branch. The framework now makes branch identity a project fact recorded in AGENTS.md, not a default inherited from examples.

Validation

  • git diff --cached --check passed.
  • Text sweep for stale usually main style wording completed; remaining main mentions are explicit examples or warnings not to assume it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants