git-workflow

The Squad branching model is a git version control strategy using dev, insiders, and main branches to structure feature development, testing, and release management. It ensures a dev-first workflow with a structured promotion pipeline.

To manage parallel development across multiple issues, use git worktree alongside the Squad branching model. This approach supports concurrent multi-issue work and handles scenarios where development spans multiple repositories.

To create a feature branch in the Squad workflow, checkout and pull the dev branch, then create a new branch named squad/{issue-number}-{slug}. This naming convention defines the issue branch for structured tracking.

Yes, the Squad branching model explicitly supports multi-repository scenarios. It manages structured workflows for feature development and release management across multiple repositories during parallel multi-issue work.

The promotion pipeline in this branching model moves code from the dev branch to insiders, and finally to main. This structured workflow ensures proper testing and release management before deploying features.

While the Squad branching model enforces branch naming and promotion pipelines, using git worktree is required for parallel multi-issue work. Without it, managing concurrent development across multiple repositories becomes unstructured.