Let's take a look at the difference between git fetch and git pull
Both git fetch and git pull can update the remote repository to the local one. So what are the differences between them? There are several concepts that have to be mentioned to clarify this issue.
Recommendation (free): Git
FETCH_HEAD: is a version link, recorded in a local file , pointing to the end version of the branch that has been taken down from the remote repository.
commit-id: After each local work is completed, a git commit operation will be performed to save the current work to the local repo. At this time, a commit-id will be generated, which is a unique A serial number that identifies a version. After using git push, this serial number will also be synchronized to the remote warehouse.
With the above concepts, let’s talk about git fetch
git fetch: This will update the latest commit-id of the branches contained in all remote warehouses in git remote and record it Go to the .git/FETCH_HEAD file
The way to update the remote warehouse with git fetch is as follows:
git fetch origin master:tmp //在本地新建一个temp分支,并将远程origin仓库的master分支代码下载到本地temp分支 git diff tmp //来比较本地代码与刚刚从远程下载下来的代码的区别 git merge tmp //合并temp分支到本地的master分支 git branch -d temp //如果不想保留temp分支 可以用这步删除
(1) If you use git fetch directly, the steps are as follows:
- Create and Update the local remote branch. That is, create and update the origin/xxx branch, and pull the code to the origin/xxx branch.
- Set the current branch-origin/current branch correspondence in FETCH_HEAD. If you directly git merge at that time, origin/abc can be merged into the abc branch.
(2) git fetch origin
Just manually specify the remote to fetch. When no branch is specified, it usually defaults to master
(3) git fetch origin dev
specifies remote remote and FETCH_HEAD, and only pulls the commits of this branch.
git pull: First, based on the local FETCH_HEAD record, compare the local FETCH_HEAD record with the version number of the remote warehouse, and then git fetch obtains the subsequent version data of the remote branch currently pointed to. , and then use git merge to merge it with the local current branch. So can be considered that git pull is a combination of the two steps of git fetch and git merge.
The usage of git pull is as follows:
git pull <远程主机名> <远程分支名>:<本地分支名> //取回远程主机某个分支的更新,再与本地的指定分支合并。
Therefore, git fetch is get the latest version from the remote to the local, but will not automatically merge.
And git pull will obtain all remote indexes and merge them into the local branch . When the effect is the same, git pull will be faster.
The above is the detailed content of Let's take a look at the difference between git fetch and git pull. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions and supports local operations; GitHub provides online collaboration tools such as Issue tracking and PullRequest.

Git and GitHub are not the same thing. Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions, and GitHub provides an online collaboration environment.

GitHub is not difficult to learn. 1) Master the basic knowledge: GitHub is a Git-based version control system that helps track code changes and collaborative development. 2) Understand core functions: Version control records each submission, supporting local work and remote synchronization. 3) Learn how to use: from creating a repository to push commits, to using branches and pull requests. 4) Solve common problems: such as merge conflicts and forgetting to add files. 5) Optimization practice: Use meaningful submission messages, clean up branches, and manage tasks using the project board. Through practice and community communication, GitHub’s learning curve is not steep.

On your resume, you should choose to write Git or GitHub based on your position requirements and personal experience. 1. If the position requires Git skills, highlight Git. 2. If the position values community participation, show GitHub. 3. Make sure to describe the usage experience and project cases in detail and end with a complete sentence.

Microsoft does not own Git, but owns GitHub. 1.Git is a distributed version control system created by Linus Torvaz in 2005. 2. GitHub is an online code hosting platform based on Git. It was founded in 2008 and acquired by Microsoft in 2018.

Starting from Git is more suitable for a deep understanding of version control principles, and starting from GitHub is more suitable for focusing on collaboration and code hosting. 1.Git is a distributed version control system that helps manage code version history. 2. GitHub is an online platform based on Git, providing code hosting and collaboration capabilities.

The reason for using GitHub to manage HTML projects is that it provides a platform for version control, collaborative development and presentation of works. The specific steps include: 1. Create and initialize the Git repository, 2. Add and submit HTML files, 3. Push to GitHub, 4. Use GitHubPages to deploy web pages, 5. Use GitHubActions to automate building and deployment. In addition, GitHub also supports code review, Issue and PullRequest features to help optimize and collaborate on HTML projects.

Git is an open source distributed version control system that helps developers track file changes, work together and manage code versions. Its core functions include: 1) record code modifications, 2) fallback to previous versions, 3) collaborative development, and 4) create and manage branches for parallel development.
