Files not updating using 'git pull'

Question

I am using Git to cooperate with other users, but today I cannot get the latest change on some files using "git pull", and I cannot see the changes in "git log".

What could be the issue?

It seems nothing is there to get the updates. Are you sure the files are committed correctly by other user and in the same repository? No Logs gives a doubt in this direction. — Aditya, Dec 14 '13 at 10:11
Are you sure you sub ordinates have pushed to the branch you are trying to pull ? — Balram Tiwari, Dec 14 '13 at 10:12
I'm having the same issue (I'm the only one at work with this issue). It's driving me batty! For the past few days I've been doing manual merges because pulls just aren't happening. But the manual merge causes all sorts of warnings to go off, which scares the entire team. — SMBiggs, Mar 02 '16 at 17:58
What is your error message or what is your ouput of the git pull command? — Strubbl, Jun 18 '20 at 19:01
This happened to me more than once in git. It's very weird. I've used hg for more then 15 years and it's never happened. — Iasmini Gomes, Jul 02 '20 at 00:28
I have been visiting this page so ofthen that I added it to favorites list. — Kemsikov, May 24 '22 at 16:14

score 58 · Answer 1 · edited Dec 12 '21 at 14:55

58

what worked for me is ,

remove .git folder
copy .git from other repo
now git checkout

Before Removing , You can try

git fetch --all 
git reset --hard origin/master

You will need to replace master with the appropriate branch, which now defaults to main.

edited Dec 12 '21 at 14:55

Ian Campbell

23,484
14
36
57

answered May 04 '18 at 07:26

ganesh

2,024
16
17

4

The last two steps (fetch and reset) worked for me. Btw, "copy .git from other repo" shouldn't work, as each .git contains info specific to the repo it belongs to. – Gaurav Singh Jun 12 '19 at 06:44
2

```git reset --hard origin/[my branch]``` worked for me. But can anyone explain why git pull just stopped working and that worked? – momo668 Feb 25 '23 at 10:56

score 25 · Answer 2 · answered Nov 29 '18 at 05:58

25

What worked for me,

git reset --hard origin/master

It showed me that some file names were too long for git to pull them from my repo and hence the mismatch and incorrect builds.

So I ran following to fix and did a hard reset again.

git config --system core.longpaths true

Thankfully it worked.

answered Nov 29 '18 at 05:58

coretechie

1,050
16
38

wouldn't this have some consequences? – PatXio Jan 21 '21 at 14:59
Like now we can name and push/pull files with long names? I dont think it would break anything and I am not sure if it came from any GIT or Java standards. – coretechie Apr 28 '22 at 06:59

score 11 · Answer 3 · edited Jan 16 '18 at 21:14

11

In my case the issue was me having an index.lock file in my .git folder. I removed that, and pull worked.

edited Jan 16 '18 at 21:14

Peter Mortensen

30,738
21
105
131

answered Mar 01 '17 at 16:33

Alwyn Schoeman

467
7
13

3

For some reason, Git doesn't mention this! – CBHacking Apr 06 '17 at 20:16
My `index.lock` file had 0 bytes, deleted it, and voila. – skinnedpanda Aug 23 '22 at 17:17
This has worked for me also – Rinsha Rinz Apr 03 '23 at 11:15

score 7 · Answer 4 · edited May 23 '17 at 12:09

7

Check your current branch.

git status
git branch

If you are not in a branch, you are in a detached HEAD mode and git pull wouldn't merge anything.

git log --all --branches

That git log will help make sure you see if there are any new commits on fetched branches (that is, the remote tracking branches).
I use that git log alias to display those commits as a graph.

edited May 23 '17 at 12:09

Community

1
1

answered Dec 14 '13 at 10:15

VonC

1,262,500
529
4,410
5,250

2

Good thinking. Cover the edge cases. – Laereom Jan 16 '18 at 20:27

score 7 · Answer 5 · edited Jan 16 '18 at 21:12

7

You could have an unfinished merge that prevents the pull. Check if you have a commit in progress.

edited Jan 16 '18 at 21:12

Peter Mortensen

30,738
21
105
131

answered Dec 14 '13 at 13:23

Lucas Czekaj

71
1

15

How do you check to see if there's a commit in progress? – SMBiggs Mar 02 '16 at 17:55

score 5 · Answer 6 · edited Oct 13 '22 at 18:02

5

It worked for me:
Instead of

$ git pull

Use

$ git pull [remote] [local-branch>

edited Oct 13 '22 at 18:02

Anbuselvan Rocky

606
6
22

answered Jun 06 '22 at 05:55

Shadyar

709
8
16

4

it worked for me: `git pull origin master` it did work I guest my upstream setup was wrong... – Alvaro Silvino Jun 22 '22 at 12:13

score 1 · Answer 7 · answered Jan 19 '17 at 15:52

I just wanted to add another case where this could happen. I was using a sparse checkout. For some reason I had a directory in my working tree that I thought was included in the sparse checkout (I thought it was listed in .git/info/sparse-checkout) but wasn't (I had removed it from .git/info/sparse-checkout for some reason I now forget.) So it was just being ignored by pull or checkout or reset or any other commands. It was very confusing until I started replicating the sparse checkout configuration in a new, fresh clone and realized the error.

This would only happen to you if you are using a sparse checkout. If you are not using a sparse checkout, it couldn't happen. (Check git config to see if sparseCheckout is enabled, and check for the existence of .git/info/sparse-checkout, but you would know if you were doing this since I think it has to be set up manually by the user anyway.) (Google it if you're curious what it is-- its just a simple mechanism to omit files and directories from a checkout that would otherwise be tracked/pulled/fetched etc.)

score 1 · Answer 8 · answered Nov 29 '21 at 17:00

I had the same issue with our enterprise Gitlab repo which recently changed from HTTPS to SSH. As my repo still used HTTPS, any git pull got silently ignored.

After changing the origin to SSH, everything went smooth again.

git remote set-url origin git@gitlab.yourdomain.com:username/repo.git

(To get the SSH URL just click the "Clone" button in your Gitlab/Github web interface and select "Clone with SSH")

score 0 · Answer 9 · answered Nov 11 '19 at 06:53

0

There are 2 possible sceanrios:
1. If you have any account in Bitbucket, gitlab and etc.
You might have to synchronise with your fork directory first and then perform git pull on your local branch. Basically you have to rebase your fork copy to get in sync with remote master and perform git pull in your local copy.
2. Just try to rebase your local work copy to be in sync with remote master.

answered Nov 11 '19 at 06:53

Vinod Kumar

562
5
12

How do we rebase the local copy to sync with remote master? – RBT Dec 12 '21 at 12:28

score 0 · Answer 10 · answered Jun 18 '20 at 18:42

0

git reset --hard origin/master

works for me but you have to go inside the folder and then use this command not only on the parent folder.

answered Jun 18 '20 at 18:42

Krishan Gopal

11

score 0 · Answer 11 · answered Jan 12 '21 at 10:53

0

for me it was commits that I made locally. These commits modify something I want to pull. So git pull doesn't get the file from origin

answered Jan 12 '21 at 10:53

loser8

362
3
14

score 0 · Answer 12 · answered May 20 '22 at 15:13

For me the FETCH_HEAD file did not have all the branches, because my newest branch was not tracked So I:

To force delete a branch (from outside that branch)

git branch -D <branch_name>

To create a new branch from a given branch

git fetch origin <remote_branch>:<local_branch>

To make the remote branch a tracking branch

git push --set-upstream origin <branch_name>

then to test it with git fetch, I noticed my FETCH_HEAD file was now correctly updated.

score 0 · Answer 13 · answered Aug 26 '23 at 05:27

0

In my case, the FETCH_HEAD was broken somehow.

When I checked it using git branch -avv, my branch was tracking the wrong commit. Even using a commit from months before.

I solved it using git reset --hard [commit hash]

answered Aug 26 '23 at 05:27

Aminah Nuraini

18,120
8
90
108

Files not updating using 'git pull'

13 Answers13