TorbatYar/docs/development/branching-strategy.md
Mortezakoohjani 12c8615615 Ship enterprise Accounting FE/API with CRUD parity and production wiring.
Adds accounting-service PATCH/archive, fiscal helpers, COA templates and setup status, plus SuperApp Accounting UI (DS, scoreboard, masters, vouchers, ledger, ops modules) with session refresh and HTTPS public API URLs.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-24 15:26:43 +03:30

1009 B

Branching Strategy

Branches

Branch Purpose
main Production-ready history
develop Integration branch for upcoming release
feature/* Feature or docs work branched from develop
hotfix/* Urgent production fixes from main
release/* Release hardening, version bumps, notes

Flow

  1. Create feature/<short-name> from develop.
  2. Open PR into develop.
  3. Cut release/x.y.z when stabilizing.
  4. Merge release into main and back into develop.
  5. Tag main with vX.Y.Z.
  6. Hotfixes merge to main and cherry-pick/merge back to develop.

Version Tagging

Semantic tags: vMAJOR.MINOR.PATCH — see release-strategy.md.

Documentation Branches

Documentation-only work still uses feature/* and must update registries/progress when claiming phase completion.