Why use fetch instead of pull?

fetch lets you inspect changes before merging them. It's safer in a team project or when you want to review what changed before touching your local code.

What happens after a fetch?

Changes are stored in remote-tracking branches (origin/main, etc.) but your local code hasn't changed. You can inspect them with git log or git diff, then merge manually.

Does git fetch delete my local changes?

No, never. That's the main advantage of fetch: it doesn't touch anything in your working directory. Your files remain exactly as they were.

Should I run git fetch regularly?

Yes, it's a good habit. Run a fetch to check if your team has pushed any code. Some developers do it at the start of the day or before creating a branch.

It's the local copy of the main branch from the remote repository (origin). When you run git fetch, this copy is updated. It's a read-only reference.

Git fetch: download without merging

git fetch downloads changes from the remote repository without touching your local code. You can inspect the changes before deciding what to do with them.

Practice git fetch Git Glossary

gitquest — enquête

Safe

What is git fetch?

git fetch downloads changes from the remote repository without merging them into your local code. Unlike git pull, it doesn't modify your working directory.

It's like checking your tracking number without opening the package. You know what has arrived, but you decide when and how to integrate it.

Git fetch syntax

git fetch origin

Download everything from origin

git fetch origin main

Download only the main branch

git fetch --all

Download from all remotes

Git fetch in practice

Download changes, inspect then merge.

Basic fetch

gitquest — fetch

# Download remote changes

$git fetch origin

remote: Enumerating objects: 8, done.

remote: Counting objects: 100% (8/8), done.

From github.com:team/project

a1b2c3d..e4f5g6h main -> origin/main

* [new branch] feature-x -> origin/feature-x

# Your local files have not changed!

Inspect then merge

gitquest — fetch + merge

# See what changed on the remote

$git fetch origin

$git log HEAD..origin/main --oneline

e4f5g6h fix: fix the form

c3d4e5f feat: add validation

# Looks good, let's merge

$git merge origin/main

Fast-forward — 2 files changed

git fetch vs git pull

`git fetch`

Downloads remote changes without merging them. Your local code stays intact.

Use when: you want to inspect before merging

`git pull`

Performs a fetch then a merge automatically. Faster but less control.

Use when: you want to update quickly

Common mistakes with git fetch

Thinking fetch updated your code

Fetch does not modify your local files. After a fetch, you still need to run git merge origin/main to integrate the changes.

Forgetting to merge after fetch

If you fetch but never merge, your local branch falls behind. Remember to merge regularly.

Confusing local and remote branches

After a fetch, origin/main is up to date but main (local) is not. These are two different references.

Part of the Git Remote & Collaboration guide

Related commands

git pull

Fetch + merge in one command

git remote

Manage remote repositories

git log

View commit history

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

Questions about git fetch

Explore remote workflows with GitQuest

Learn to navigate between local and remote through GitQuest challenges.

Start the investigations