Git Notes
HubBenefits of Git and GitHub - Why They MatterGit vs GitHubVersion Control SystemWhat Is GitWhat Is GitHubConfigure Git - User Identity and SettingsCreate GitHub Account - Sign Up GuideFirst Git Repository - Getting StartedInstall Git on Linux - Complete Setup GuideInstall Git on macOS - Installation GuideInstall Git on Windows - Step-by-Step GuideGit Add - Stage ChangesGit Clone - Copy Remote Repositories LocallyGit Commit - Save ChangesGit Diff - Compare Changes in Your RepositoryGit Ignore - Exclude Files from Version ControlGit Init - Initialize RepositoryGit Log - View Commit HistoryGit Status - Check Repository StateGit Fetch - Download Remote Changes Without MergingGit Pull - Fetch and Merge Remote ChangesGit Push - Upload Local Commits to Remote RepositoryGit Remote - Manage Remote Repository ConnectionsLocal Repository - Understanding Your Git Working EnvironmentRemote Repository - Collaborate Through Shared RepositoriesSync Local and Remote - Keep Repositories in HarmonyAmend Commit - Fix Last CommitDelete Branch - Clean Up BranchesGit Reset - Move HEAD and Undo CommitsGit Restore - Discard ChangesGit Revert - Safely Undo ChangesRecover Lost Commits - Reflog GuideFork RepositoryGitHub PagesGitHub Profile SetupGitHub RepositoriesGitHub Stars and WatchersRepository SettingsCode ReviewsGit CloneGit FetchGit PullGit PushGitHub IssuesLabels and MilestonesOpen Source ContributionsGitHub Project BoardsPull Requests - Propose and Review Code ChangesTeam Collaboration with Git and GitHubAutomated Testing with GitHub ActionsCI/CD with GitHub ActionsDeployment Automation with GitHub ActionsIntroduction to GitHub ActionsGitHub Actions RunnersGitHub Actions WorkflowsEnterprise Git Workflows - Scale Git for Large OrganizationsFeature Branch Workflow - Isolate Development WorkGitFlow Workflow - Structured Release ManagementMonorepo Workflow - Manage Multiple Projects in One RepositoryTrunk-Based Development - Ship Code Fast and SafelyDeployment WorkflowsGitHub Pages DeploymentNetlify Deployment from GitHubRender Deployment from GitHubVercel Deployment from GitHubBranch Protection Rules - Secure Your Git BranchesPersonal Access Tokens - Authenticate with GitHubRepository Security Best PracticesSecret Scanning - Detect Leaked Credentials in CodeSigned Commits - Verify Commit Authenticity with GPGSSH Keys - Secure Git Authentication Without PasswordsGit Bisect - Find Bugs with Binary SearchGit Cherry-Pick - Apply Specific Commits to Any BranchGit Hooks - Automate Workflows with Git EventsGit Internals - Understanding How Git Works Under the HoodGit Stash - Temporarily Save Uncommitted ChangesGit Submodules - Manage External Dependencies as Git ReposGit Tag - Mark Important Points in HistoryGit Worktrees - Work on Multiple Branches SimultaneouslyCollaborative Web App ProjectComplete Team Workflow ProjectGitHub Actions Project - Build a CI/CD PipelineOpen Source Project Contribution - Guided ExercisePortfolio Project with Git - Showcase Your SkillsGit Command CheatsheetGit Interview Questions - Comprehensive Preparation GuideGitHub Interview QuestionsScenario-Based Git Interview QuestionsGit Troubleshooting GuideGit Best Practices - Professional Development HabitsCommon Git Errors and Fixes - Quick SolutionsGit Command Reference - Complete Command GuideLearning Resources - Continue Your Git & GitHub EducationBranch Strategies - Choosing the Right Git Branching ModelCreate Branch in Git - Start New Development LinesFast-Forward Merge in Git - Clean Linear HistoryGit BranchGit CheckoutGit MergeGit RebaseMerge Branches in Git - Combine Development WorkMerge Conflicts - Resolve Git Conflicts Like a ProSwitch Branch in Git - Navigate Between Branches
Learn how git fetch downloads remote changes without modifying your working directory. Understand fetch vs pull, remote tracking branches, and fetch strategies.
Git fetch downloads commits, files, and refs from a remote repository into your local repo without modifying your working directory or current branch. It is a safe way to review changes before integrating them.
Fetch vs Pull
┌────────────────────────────────────────────────────────────┐
│ │
│ git fetch = Download only (safe, non-destructive) │
│ git pull = Download + Merge (modifies working directory) │
│ │
│ git pull = git fetch + git merge │
│ │
└────────────────────────────────────────────────────────────┘
| Aspect | git fetch | git pull |
|---|---|---|
| Downloads changes | ✅ Yes | ✅ Yes |
| Modifies working dir | ❌ No | ✅ Yes |
| Merges automatically | ❌ No | ✅ Yes |
| Can cause conflicts | ❌ No | ✅ Possible |
| Safe to run anytime | ✅ Yes | ⚠️ May disrupt work |
Basic Fetch Commands
Fetch from Default Remote (origin)
bash example
git fetchOutput
remote: Enumerating objects: 12, done. remote: Counting objects: 100% (12/12), done. remote: Compressing objects: 100% (8/8), done. remote: Total 12 (delta 4), reused 8 (delta 3) Unpacking objects: 100% (12/12), done. From https://github.com/user/repo a1b2c3d..e5f6g7h main -> origin/main * [new branch] feature/x -> origin/feature/x
Fetch from a Specific Remote
bash example
git fetch origin
git fetch upstreamFetch All Remotes
bash example
git fetch --allOutput
Fetching origin Fetching upstream From https://github.com/original/repo f7e8d9c..a1b2c3d main -> upstream/main
Fetch a Specific Branch
bash example
git fetch origin mainWhat Happens After Fetch
After fetching, remote tracking branches are updated:
bash example
# Your local branches (unchanged)
git branchOutput
* feature/auth main
bash example
# Remote tracking branches (updated by fetch)
git branch -rOutput
origin/main ← Updated by fetch origin/feature/auth origin/feature/new ← New branch from fetch
bash example
# Compare your branch with fetched remote
git log main..origin/main --onelineOutput
e5f6g7h Update API documentation d4e5f6g Add error handling middleware c3d4e5f Fix authentication bug
These commits exist on the remote but not in your local main yet.
Reviewing Fetched Changes
bash example
# See what changed on remote main
git log origin/main --oneline -5Output
e5f6g7h (origin/main) Update API documentation d4e5f6g Add error handling middleware c3d4e5f Fix authentication bug b2c3d4e Refactor user service a1b2c3d (HEAD -> main) Initial commit
bash example
# See diff between local and remote
git diff main origin/mainbash example
# See commit details
git show origin/mainIntegrating Fetched Changes
After reviewing, merge or rebase:
bash example
# Option 1: Merge
git checkout main
git merge origin/main
# Option 2: Rebase
git checkout main
git rebase origin/mainFetch with Prune
Remove local references to deleted remote branches:
bash example
git fetch --prune
# or
git fetch -pOutput
From https://github.com/user/repo - [deleted] (none) -> origin/feature/old-branch - [deleted] (none) -> origin/feature/merged-branch a1b2c3d..e5f6g7h main -> origin/main
Auto-Prune on Every Fetch
bash example
git config --global fetch.prune trueFetch Tags
bash example
# Fetch all tags
git fetch --tags
# Fetch without tags
git fetch --no-tagsShallow Fetch
bash example
# Fetch only recent history
git fetch --depth 1 origin main
# Deepen an existing shallow clone
git fetch --deepen 10Practical Workflows
Safe Update Check
bash example
# Check for updates without disrupting work
git fetch origin
# See if main has moved ahead
git log HEAD..origin/main --oneline
# If output is empty, you are up to date
# See if your branch is behind
git statusOutput
On branch feature/auth Your branch is behind 'origin/feature/auth' by 3 commits, and can be fast-forwarded.
Pre-Merge Review
bash example
# Before merging a PR locally
git fetch origin
git log origin/feature/new-feature --oneline -10
git diff main..origin/feature/new-feature --statInterview Questions
- What is the difference between git fetch and git pull?
git fetch downloads remote changes and updates remote tracking branches without modifying your working directory. git pull does a fetch followed by a merge (or rebase), which modifies your current branch.
- Why would you use git fetch instead of git pull?
Fetch is safer — it lets you review changes before integrating them. You can see what others have pushed, compare branches, and decide how to merge without risking conflicts in your working directory.
- What are remote tracking branches?
Remote tracking branches (like origin/main) are local references that track the state of branches on remote repositories. They are updated by git fetch and show where remote branches were at the last fetch.
- What does
git fetch --prunedo?
It removes local remote-tracking references for branches that no longer exist on the remote server, keeping your local reference list clean.
- Does git fetch modify any local branches?
No. Git fetch only updates remote tracking branches (refs/remotes/). Your local branches, working directory, and staging area remain completely untouched.
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Git Fetch - Download Remote Changes Without Merging.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this Git & GitHub topic.
Search Terms
git-github, git & github, git, github, working, with, repositories, fetch
Related Git & GitHub Topics
Continue learning this concept
Working With RepositoriesGit Pull - Fetch and Merge Remote ChangesLearn how to use git pull to download and integrate remote changes. Understand pull strategies, pull with rebase, handling conflicts, and best practices.Working With RepositoriesGit Push - Upload Local Commits to Remote RepositoryLearn how to use git push to share your commits with remote repositories. Cover push options, force push, upstream tracking, and push best practices.Working With RepositoriesGit Remote - Manage Remote Repository ConnectionsLearn how to add, remove, rename, and manage remote repositories in Git. Understand multiple remotes, upstream tracking, and remote URL configuration.Working With RepositoriesLocal Repository - Understanding Your Git Working EnvironmentLearn about local Git repositories, the working directory, staging area, and local commit history. Understand how Git manages files on your machine.Working With RepositoriesRemote Repository - Collaborate Through Shared RepositoriesUnderstand remote repositories in Git, how they enable collaboration, hosting platforms, and the relationship between local and remote repos.Working With RepositoriesSync Local and Remote - Keep Repositories in HarmonyLearn workflows for synchronizing local and remote Git repositories. Master fetch-merge-push cycles, handling diverged branches, and staying up to date.