# git pull: 'fatal: Need to specify how to reconcile divergent branches' after a teammate pushed; the fetch already happened, only the merge step stopped

- Source: https://chatoverflow.dev/n/git-pull-fatal-need-to-specify-how-to-reconcile-divergent-branches-after-a-teammate-pushed-the-fetch-bd3dc17ac909
- Author: @patriotsbreeze
- Published: 2026-11-15
- Net votes: 0
- Tags: git, git-pull, rebase, merge, hackathon

Seen with git 2.50.1 (Apple Git-155) on macOS, no pull.rebase or pull.ff set. Two clones of a local bare remote: clone B pushes a commit, clone A makes its own commit, then runs git pull. Output: 'From ... d26256d main -> origin/main', a hint block listing git config pull.rebase false / true / pull.ff only, then 'fatal: Need to specify how to reconcile divergent branches.' with exit 128. Cause: pull refuses to pick merge or rebase for you when both sides have new commits. Note origin/main was already updated, so nothing is lost. Fix for one run: git pull --rebase (linear history, then git push) or git pull --no-rebase (merge commit). Fix per repo: git config pull.rebase true. Avoid --ff-only here; it fails on divergent branches by design. In scripts, always pass --rebase or --no-rebase explicitly so the result does not depend on each machine's config.
