Repository navigation
REQ 010
This repository's branch governance shall follow GitFlow (develop, feature/*, release/*, hotfix/*), per ADR-0001.
Required to satisfy repo-standards-review's CM gate, per operator decision (VITechnologies/projectbuddy#6).
A develop branch exists alongside main; releases are cut via release/vX.Y.Z branches merged to both main and develop (or confirmed as a legitimate no-op merge-back if the two are already content-identical), never tagged directly off ad-hoc commits to main.
Live-verified: v0.3.9-v0.3.27 were all cut through the full release/* flow (see docs/release/release-procedure.md and each release's own PR history). v0.3.28 has one disclosed, judged exception (a non-release PR landed directly on main after its release branch's own promotion, to ship a real-CI-dispatch-discovered parse-error fix without cutting a second release branch for one two-line change) -- recorded in docs/cm/cm-plan.md's Status Accounting section, not a silent deviation.
Software-Requirements-Specification
High
Live: v0.3.9-v0.3.27 cut via full release/* flow; v0.3.28 has one disclosed, judged exception (a post-release-branch direct-to-main fix, see docs/cm/cm-plan.md Status Accounting)
docs/release/release-procedure.md, docs/architecture/adr/ADR-0001-adopt-gitflow-for-release-governance.md
Verified (live), with 1 disclosed exception