git-workflow

To prevent unsafe merges, standardize a three-branch git workflow using dev for integration, main for released code, and insiders for early access. This model applies branch naming conventions, draft PRs, and worktree isolation to ensure safe, repeatable releases.

The dev-first git workflow model starts all feature work from the dev branch to standardize integration. It uses a three-branch structure with dev, main, and insiders, applying per-issue branches and worktree isolation to coordinate team releases.

Set up git worktrees for parallel feature development using per-worktree isolation with dedicated branch naming conventions. This dev-first workflow applies squad/{issue-number}-{slug} branches to enable isolated draft PR workflows and safe merges.

In a three-branch git workflow model, use the naming convention squad/{issue-number}-{slug} for issue tasks. This standardizes per-issue branches linked to draft PR workflows, ensuring repeatable releases and maintaining repo hygiene across dev, main, and insiders.

You need an insiders branch for early access releases when coordinating feature work across a three-branch git workflow. It separates early access code from main released code and dev integration, preventing misaligned releases while applying safe merge guardrails.

Clean up branches after a merge by applying standardized post-merge release procedures within the three-branch git workflow. This maintains repo hygiene by removing merged squad/{issue-number}-{slug} branches and ensuring dev, main, and insiders stay synchronized.