Fetch vs pull difference in Git - Quick Revision & Key Differences

Recall & Review

beginner

What does git fetch do?

git fetch downloads new data from a remote repository but does not change your working files. It updates your local copy of the remote branches.

beginner

What does git pull do?

git pull downloads new data from a remote repository and immediately merges it into your current working branch, updating your files.

intermediate

How is git pull related to git fetch?

git pull is like running git fetch followed by git merge. It fetches changes and then merges them automatically.

intermediate

Why might you use git fetch instead of git pull?

You use git fetch when you want to see changes from others without changing your current files. It lets you review updates before merging.

intermediate

What happens if there are conflicts during a git pull?

If there are conflicts, git pull will pause and ask you to fix the conflicts manually before completing the merge.

What does git fetch do?

A Creates a new branch

B Downloads and merges changes automatically

C Downloads changes but does not update working files

D Deletes local branches

git fetch only downloads changes from the remote but does not change your current files.

Which command updates your current branch with remote changes immediately?

A git pull

B git fetch

C git clone

D git status

git pull downloads and merges remote changes into your current branch.

What is the sequence of commands that git pull performs internally?

A git fetch then git merge

B git merge then git fetch

C git commit then git push

D git clone then git checkout

git pull runs git fetch first, then git merge.

Why might you prefer git fetch over git pull?

A To automatically merge changes

B To push local changes

C To delete remote branches

D To review changes before merging

git fetch lets you see remote changes without merging, so you can review first.

What must you do if git pull results in conflicts?

A Ignore and continue

B Fix conflicts manually before completing merge

C Run <code>git push</code> immediately

D Delete your local branch

You must fix conflicts manually before the merge can finish.

Explain the difference between git fetch and git pull in your own words.

Think about what happens to your files after each command.

Describe a situation where using git fetch is better than git pull.

Consider when you want to be cautious before changing your files.

Practice

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