What should I do if the code pulled by git pull is not updated?

The git pull pull code is not updated. Solution: 1. git pull does not update the file due to lack of information; 2. git pull does not update the file due to uncommitted files in the local warehouse.

The git pull functionality can malfunction for a number of reasons. We'll look at common causes and how to fix them.

git pull did not update file due to missing information

When Git does not have enough information to work with, you may receive an error message as shown below.

$ git pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull
If you wish to set tracking information for this branch you can do so
with:
git branch --set-upstream-to=/ master

If you receive a message like this, Git will ask you to specify a remote branch to track your current local branch. Use git branch --set-upstream-to=/master command, then run the git pull command to point Git to the source you wish to change.

git pull does not update files due to uncommitted files in the local repository

As a source code management system, Git does its best to prevent you from losing files and data. For this reason, Git may perform a git pull Refuses to merge your local files with files in the remote repository when commanded.

Since Git does not have a forced git pull command, you can call the system to merge the changes. If you have uncommitted changes, you may receive an error message like the one below.

$ git pull
From REPOSITORY_URL
* branch master -> FETCH_HEAD
a152b19..171e4a2 master -> origin/master
Updating a152b19..171e4a2
error: Your local changes to the following files would be overwritten by
merge:
file1.txt
file2.txt
Please commit your changes or stash them before you merge.
Aborting

To solve this problem, run the git stash command to store your local changes before running the git pull command.

The final step is to run git stash apply after the git pull command. This command will apply hidden changes to your working directory.

$ git stash
Saved working directory and index state WIP on master: d91368b Previous
commit message
$ git pull
From REPOSITORY_URL
* branch master -> FETCH_HEAD
a152b19..171e4a2 master -> origin/master
Updating a152b19..171e4a2
Fast-forward
file1.txt | 1 +
file2.txt | 1 +
2 files changed, 2 insertions(++)
$ git stash apply

You can also commit changes before running the git pull command.

$ git commit -am 'Committing two files before git-pull'
[master d91368b] Committing two files before git-pull
2 files changed, 2 insertions(++)
$ git pull
From REPOSITORY_URL
* branch master -> FETCH_HEAD
a152b19..171e4a2 master -> origin/master
Updating a152b19..171e4a2
Fast-forward
file1.txt | 1 +
file2.txt | 1 +

2 files changed, 2 insertions( )

If you don’t need the local changes, you can discard them before running the git pull command.

You can use the git rest --hard command to discard untracked files. Make sure you don't need these changes as you can't undo the discard.

The above is the detailed content of What should I do if the code pulled by git pull is not updated?. For more information, please follow other related articles on the PHP Chinese website!