git-workflow

A dev-first three-branch git workflow uses main for released code, dev for integration, and insiders for early access. It prevents direct work on main, coordinating releases through staged promotion pipelines to improve predictability and review cycles.

To start feature development in a three-branch model, begin from the dev branch and create a squad/issue-number-slug feature branch. Implement your changes there, then open a draft PR targeting dev for integration and review.

Yes, the git workflow supports parallel worktrees for multi-repo coordination. It provides documented procedures and common workflow guidelines for managing parallel worktrees alongside single-issue work within the dev and insiders branch structure.

Code progresses through an automated promotion pipeline from dev to insiders, and finally to main. This staged release process ensures validation occurs at each step before merging changes into the protected main branch.

An insiders branch provides early access and syncs for upcoming releases. It separates staged features from the dev integration branch, reducing coordination risks and allowing teams to validate code before final promotion to main.