# Git & Worktrees SF uses git for milestone isolation and sequential commits. The strategy is fully automated — you don't need to manage branches manually. ## Isolation Modes SF supports three isolation modes, configured via `git.isolation` in preferences: | Mode | Working Directory | Branch | Best For | |------|-------------------|--------|----------| | `worktree` (default) | `.sf/worktrees//` | `milestone/` | Most projects — full isolation | | `branch` | Project root | `milestone/` | Submodule-heavy repos | | `none` | Project root | Current branch | Hot-reload workflows | ### Worktree Mode (Default) Each milestone gets its own git worktree and branch. All execution happens inside the worktree. On completion, everything is squash-merged to main as one clean commit. The worktree and branch are then cleaned up. Changes in a milestone can't interfere with your main working copy. ### Branch Mode Work happens in the project root on a `milestone/` branch. No worktree directory is created. Useful when worktrees cause problems with submodules or hardcoded paths. ### None Mode Work happens directly on your current branch. No worktree, no milestone branch. SF still commits with conventional commit messages. Use this when file isolation breaks dev tooling (file watchers, hot-reload, etc.). ## Branching Model ``` main ──────────────────────────────────────────── │ ↑ └── milestone/M001 (worktree) ─────────────┘ commit: feat: core types commit: feat: markdown parser commit: feat: file writer → squash-merged to main ``` ## Workflow Modes Set `mode` for sensible defaults instead of configuring each setting individually: ```yaml mode: solo # personal projects mode: team # shared repos ``` | Setting | `solo` | `team` | |---------|--------|--------| | `git.auto_push` | `true` | `false` | | `git.push_branches` | `false` | `true` | | `git.pre_merge_check` | `false` | `true` | | `unique_milestone_ids` | `false` | `true` | Mode defaults are the lowest priority — any explicit preference overrides them. ## Git Preferences ```yaml git: auto_push: false # push after commits push_branches: false # push milestone branch to remote remote: origin # git remote name snapshots: true # WIP snapshot commits during long tasks pre_merge_check: auto # validation before merge commit_type: feat # override conventional commit prefix main_branch: main # primary branch name merge_strategy: squash # "squash" or "merge" isolation: worktree # "worktree", "branch", or "none" commit_docs: true # commit .sf/ artifacts to git manage_gitignore: true # let SF manage .gitignore auto_pr: false # create PR on milestone completion pr_target_branch: develop # PR target branch ``` ## Automatic Pull Requests For teams using Gitflow or branch-based workflows: ```yaml git: auto_push: true auto_pr: true pr_target_branch: develop ``` When a milestone completes, SF pushes the branch and creates a PR targeting your specified branch. Requires `gh` CLI installed and authenticated. ## Post-Worktree Hook Run a script after worktree creation (copy `.env` files, symlink assets, etc.): ```yaml git: worktree_post_create: .sf/hooks/post-worktree-create ``` Example hook: ```bash #!/bin/bash cp "$SOURCE_DIR/.env" "$WORKTREE_DIR/.env" ln -sf "$SOURCE_DIR/assets" "$WORKTREE_DIR/assets" ``` ## Keeping `.sf/` Local For teams where only some members use SF: ```yaml git: commit_docs: false ``` This adds `.sf/` to `.gitignore` entirely. You get structured planning without affecting teammates who don't use SF. ## Commit Format Commits use conventional commit format with SF metadata: ``` feat: core type definitions SF-Task: M001/S01/T01 ``` ## Manual Worktree Management Use `/worktree` (or `/wt`) for manual worktree operations: ``` /worktree create /worktree switch /worktree merge /worktree remove ``` ## Self-Healing SF automatically recovers from common git issues: - **Detached HEAD** — reattaches to the correct branch - **Stale lock files** — removes `index.lock` from crashed processes - **Orphaned worktrees** — detects and cleans up abandoned worktrees Run `/sf doctor` to check git health manually.