Workflows
fetch vs pull
Explains why fetch-first workflows are often more controllable than pulling directly.
The core difference
git fetch: download remote refs and objects without directly changing your current branchgit pull: fetch first, then integrate the remote changes into your current branch
That is why many teams prefer:
git fetch origin
# inspect first, then choose merge or rebase
Why fetch is a better default habit
Fetch separates “sync remote state” from “modify my branch”.
That gives you room to inspect:
- whether the remote moved ahead
- whether your branch diverged
- whether merge, rebase, or fast-forward is the better next step