Git Fetch (original) (raw)
Last Updated : 27 Dec, 2025
git fetch is a safe and non-disruptive Git command that checks for and downloads the latest updates from a remote repository without merging them into your local branch, giving developers full control over when and how changes are integrated.
- Prevents automatic merges that may occur with git pull.
- Retrieves remote branches, tags, and references without altering local files.
- Allows developers to review and compare changes before merging them manually.
Working of Git Fetch
git fetch works by safely retrieving the latest updates from a remote repository without altering the local working branch.
- Git connects to the remote repository (commonly origin).
- It checks for new commits, branches, or updates on the remote.
- The updates are downloaded and stored as remote-tracking branches (for example, origin/main).
- Local branches remain unchanged during this process.
- Developers can later merge or rebase these fetched changes as needed.
When to Use Git Fetch
Here are some cases where git fetch is particularly useful:
- **Collaborative Projects: Fetch updates to stay informed about team changes.
- **Monitoring Remote Branches: Track remote progress without modifying local branches.
- **Inspecting Changes: Review updates before merging or rebasing.
Syntax
git fetch
- ****:** The name of the remote repository (default is origin).
- **** (optional):** The specific branch you want to fetch.
**Example:
git fetch origin
Fetches updates for all branches from the remote repository named origin.
**Example:
git fetch origin feature-branch
Fetches only the updates from the feature-branch on the remote repository.
**Example:
git fetch origin dev
Fetches the latest changes from the remote dev branch for review.
**Example:
git log origin/dev
Displays the commit history of the fetched remote dev branch.
**Example:
git fetch --all --tags
Fetches all branches and tags from all configured remote repositories.
Difference Between Git Fetch and Git Pull
Here's the difference between Git Fetch and Git Pull:
| Git Fetch | Git Pull |
|---|---|
| Checks for updates from remote without applying them | Fetches and merges changes into your current branch |
| Safe for reviewing before merging | May introduce merge conflicts immediately |
| Keeps local working directory unchanged | Alters working directory based on remote updates |
| Best for cautious syncing | Best when you're ready to integrate updates |
Advanced Usage of Git Fetch
1. Fetching and Pruning Deleted Branches
Over time, remote branches may be deleted. You can clean up stale branches with:
git fetch --prune
This command removes references to branches that no longer exist on the remote repository.
2. Fetching Specific Tags
If you want to fetch a particular tag, use:
git fetch origin tag v1.0.0
3. Shallow Fetching
In cases where bandwidth or storage is limited, you can perform a shallow fetch:
git fetch --depth=1
This fetches only the latest commit, reducing the amount of data downloaded.
Best Practices
- **Frequent Fetching: Regularly use git fetch to keep your local repository aware of the latest changes in the remote.
- **Inspect Before Merging: Always inspect fetched changes using git log or git diff before merging them into your working branch.
- **Prune Stale Branches: Use git fetch --prune to keep your branch list clean and up-to-date.