Git Workflow

Choose the smallest workflow that satisfies the repository's release, review, and support constraints. Inspect existing contribution docs and branch protection before proposing a new convention.

Workflow

1. Establish constraints:
   • release cadence and supported versions;
   • CI reliability and deployment automation;
   • review or regulatory gates;
   • team size, time zones, and merge frequency.
2. Inspect current conventions with read-only Git commands.
3. Select a model:
   • Prefer trunk-based development with short-lived branches for continuous delivery.
   • Use release branches when multiple supported versions or scheduled stabilization require them.
   • Use a GitFlow-style develop branch only when its extra integration stage solves a documented constraint.
4. Document branch, commit, review, merge, and tag rules together.
5. Test the workflow on one representative change before rolling it out.