Git Fetch: See Remote Changes Before You Merge

What is git fetch?

git fetch downloads commits, branches, and tags from a remote and updates your remote-tracking branches (like origin/main), but never changes your current branch or working directory. git pull is git fetch followed by a merge (or rebase).

Why it matters

You want to know what your teammates pushed, but git pull would merge it straight into your work. You are not ready for that, and a surprise merge conflict is the last thing you need.

git fetch downloads new commits from the remote without touching your working files or your branches. It lets you look first and decide how to integrate later, which is why many developers prefer it to git pull.

Where it usually goes wrong

• Thinking git fetch changes your local branch: it only updates remote-tracking branches such as origin/main
• Using git pull when a simple fetch and inspection would be safer
• Not fetching before comparing branches, then reviewing stale information
• Forgetting --prune, so deleted remote branches linger locally

Git fetch, step by step

1. 1

   Step 1: Fetch from the default remote

   Run git fetch to download everything new from origin. Your local branches and files stay exactly as they were.

   TerminalCopy commands

   git fetch# From github.com:you/project#    3f2a1b9..8c4d7e2  main -> origin/main

2. 2

   Step 2: See what is incoming

   Compare your branch with its remote-tracking branch. The three-dot and two-dot forms answer different questions.

   TerminalCopy commands

   # Commits on origin/main that you do not have yetgit log HEAD..origin/main --oneline# Files changed upstreamgit diff HEAD...origin/main --stat# Ahead/behind statusgit status -sb

   Tip: git status reports 'behind' only after a fetch, because that is when Git learns about the remote's state.

3. 3

   Step 3: Integrate the changes

   When you are happy with what you see, merge or rebase onto the remote-tracking branch.

   TerminalCopy commands

   # Mergegit merge origin/main# Or rebase your work on topgit rebase origin/main

4. 4

   Step 4: Fetch every remote and clean up

   --all fetches from every configured remote. --prune removes remote-tracking branches that no longer exist on the server.

   TerminalCopy commands

   git fetch --all --prune

   Tip: Enable pruning permanently with git config --global fetch.prune true.

   

5. 5

   Step 5: Check out a teammate's new branch

   After a fetch, a branch someone just pushed is available as a remote-tracking branch. Create a local branch from it.

   TerminalCopy commands

   git fetchgit switch feature/search# Creates a local feature/search tracking origin/feature/search

6. 6

   Step 6: Fast-forward a branch without checking it out

   To update a local branch you are not on, fetch directly into it. Git refuses unless it is a pure fast-forward.

   TerminalCopy commands

   git fetch origin main:main

   Careful: This does not work for the branch you currently have checked out. Use git pull --ff-only there.

Mistakes to avoid with git fetch

Expecting fetch to update your files

After git fetch your working directory is unchanged. New commits only exist under origin/<branch> until you merge or rebase.

Fix: Follow up with git merge origin/<branch> or git rebase origin/<branch>, or use git pull.

Comparing against a stale remote-tracking branch

origin/main is a local snapshot of the remote at the time of your last fetch. It does not update itself.

Fix: Run git fetch before any comparison with the remote.

Never pruning

Branches deleted on the remote stay visible in git branch -r, cluttering your list.

Fix: Use git fetch --prune or set fetch.prune to true.

Git fetch in Gitoryx

Gitoryx fetches in the background and shows incoming commits on the graph, so you see exactly what changed on the remote before you merge or rebase anything.

• Fetch with one click, or let Gitoryx fetch periodically in the background
• Incoming commits appear on the graph next to your local branch
• Ahead and behind counters show how far you diverged from the remote
• Merge or rebase from the same view once you reviewed the changes

Free plan · no account required · macOS, Windows and Linux

Git fetch: frequently asked questions

What is the difference between git fetch and git pull?

git fetch only downloads new data and updates remote-tracking branches. git pull runs git fetch and then merges (or rebases) the result into your current branch.

Is git fetch safe?

Yes. It never modifies your working directory, your index, or your local branches, so it cannot cause conflicts or lose work.

What does git fetch origin do?

It downloads new commits, branches, and tags from the remote named origin and updates the origin/* remote-tracking branches.

How often should I run git fetch?

Before you start working, before comparing branches, and before pushing. Many clients, Gitoryx included, can fetch automatically.

How do I fetch a single branch?

Run git fetch origin <branch>, for example git fetch origin main.