Bird
Raised Fist0
Gitdevops~5 mins

Fetch vs pull difference in Git - CLI Comparison

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
When working with Git, you often need to update your local copy of a project with changes from others. Fetch and pull are two commands that help you get those updates, but they work differently. Understanding the difference helps you control when and how changes are merged into your work.
When you want to see what changes are available on the remote repository without changing your local files
When you want to update your local branch immediately with remote changes
When you want to review incoming changes before merging them into your work
When you want to avoid automatic merges that might cause conflicts
When you want to keep your local repository up to date but merge changes later
Commands
This command downloads the latest changes from the remote repository named 'origin' but does not change your local files. It updates your remote tracking branches so you can review changes first.
Terminal
git fetch origin
Expected OutputExpected
remote: Enumerating objects: 5, done. remote: Counting objects: 100% (5/5), done. remote: Compressing objects: 100% (3/3), done. remote: Total 3 (delta 1), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (3/3), 1.23 KiB | 1.23 MiB/s, done.
→
origin - Specifies the remote repository to fetch from
This command fetches the latest changes from the 'main' branch on the remote 'origin' and then merges those changes into your current local branch immediately.
Terminal
git pull origin main
Expected OutputExpected
Updating 1a2b3c4..5d6e7f8 Fast-forward file.txt | 2 ++ 1 file changed, 2 insertions(+)
→
origin - Specifies the remote repository to pull from
→
main - Specifies the branch to pull changes from
Key Concept

If you remember nothing else from this pattern, remember: git fetch only downloads changes without applying them, while git pull downloads and merges changes immediately.

Common Mistakes
Using git pull when you want to review changes first
git pull merges changes immediately, which can cause unexpected conflicts or overwrite local work without review
Use git fetch first to see changes, then merge manually when ready
Assuming git fetch updates local files automatically
git fetch only updates remote tracking branches, your working files stay the same until you merge
After git fetch, use git merge or git rebase to apply changes to your local branch
Summary
git fetch downloads changes from the remote repository but does not change your local files.
git pull downloads and immediately merges changes into your current local branch.
Use git fetch to review changes before merging, and git pull to update and merge in one step.

Practice

(1/5)
1. What is the main difference between git fetch and git pull?
easy
A. git fetch deletes local changes; git pull only downloads updates.
B. git fetch downloads updates without changing files; git pull downloads and merges updates.
C. git fetch merges changes automatically; git pull only downloads updates.
D. git fetch uploads changes; git pull downloads changes.

Solution

  1. Step 1: Understand git fetch behavior

    git fetch downloads updates from the remote repository but does not change your working files or current branch.

  2. Step 2: Understand git pull behavior

    git pull downloads updates and immediately merges them into your current branch, changing your files.

  3. Final Answer:

    git fetch downloads updates without changing files; git pull downloads and merges updates. -> Option B

  4. Quick Check:

    Fetch = download only, Pull = download + merge [OK]
Hint: Fetch only downloads; pull downloads and merges [OK]
Common Mistakes:
  • Thinking fetch changes files immediately
  • Confusing pull as only download
  • Believing fetch uploads changes
2. Which of the following is the correct syntax to fetch updates from the remote repository?
easy
A. git merge origin/main
B. git pull origin main
C. git push origin main
D. git fetch origin

Solution

  1. Step 1: Identify fetch command syntax

    The correct command to download updates without merging is git fetch origin, where origin is the remote name.

  2. Step 2: Check other options

    git pull origin main downloads and merges; git push uploads changes; git merge merges branches locally.

  3. Final Answer:

    git fetch origin -> Option D

  4. Quick Check:

    Fetch syntax = git fetch [remote] [OK]
Hint: Fetch uses 'git fetch' plus remote name [OK]
Common Mistakes:
  • Using git pull instead of fetch
  • Confusing push with fetch
  • Trying to merge with fetch command
3. You run git fetch followed by git status. What will git status show regarding your branch?
medium
A. Your branch is behind 'origin/main' by some commits.
B. Your branch is up to date with 'origin/main'.
C. Your branch has uncommitted changes.
D. Your branch is ahead of 'origin/main' by some commits.

Solution

  1. Step 1: Understand effect of git fetch on local branch

    git fetch updates remote tracking branches but does not merge changes into your current branch.

  2. Step 2: Interpret git status after fetch

    If remote has new commits, git status will say your branch is behind 'origin/main' by those commits, since you haven't merged yet.

  3. Final Answer:

    Your branch is behind 'origin/main' by some commits. -> Option A

  4. Quick Check:

    Fetch updates remote info; status shows branch behind [OK]
Hint: Fetch updates remote info; status shows if behind [OK]
Common Mistakes:
  • Assuming fetch merges changes automatically
  • Thinking status shows branch up to date after fetch
  • Confusing uncommitted changes with remote updates
4. You ran git pull but got a merge conflict error. What should you do to fix this?
medium
A. Manually resolve conflicts in files, then commit the merge.
B. Delete the repository and clone again.
C. Run git reset --hard to discard local changes.
D. Run git fetch again to fix conflicts.

Solution

  1. Step 1: Understand merge conflict after git pull

    git pull merges remote changes into your branch; conflicts happen if changes clash.

  2. Step 2: Resolve conflicts properly

    You must open conflicted files, fix conflicts manually, then stage and commit the merge to complete it.

  3. Final Answer:

    Manually resolve conflicts in files, then commit the merge. -> Option A

  4. Quick Check:

    Fix conflicts manually, then commit merge [OK]
Hint: Resolve conflicts manually, then commit [OK]
Common Mistakes:
  • Rerunning fetch to fix conflicts
  • Resetting hard loses local work
  • Deleting repo is unnecessary
5. You want to review remote changes before merging them into your current branch. Which sequence of commands should you use?
hard
A. git pull then git log
B. git merge origin/main then git fetch
C. git fetch then git diff origin/main
D. git push then git pull

Solution

  1. Step 1: Fetch remote changes without merging

    Use git fetch to download remote updates without changing your files.

  2. Step 2: Review differences before merging

    Use git diff origin/main to see changes between your branch and remote branch before merging.

  3. Final Answer:

    git fetch then git diff origin/main -> Option C

  4. Quick Check:

    Fetch to download, diff to review before merge [OK]
Hint: Fetch first, then diff to review changes [OK]
Common Mistakes:
  • Pull merges immediately without review
  • Merging before fetching misses updates
  • Push uploads changes, not for review