Your configuration specifies to merge with the from the remote, but no such ref was fetched.?

Question

I am getting this error for pull:

Your configuration specifies to merge with the ref 'refs/heads/feature/Sprint4/ABC-123-Branch' from the remote, but no such ref was fetched.

This error is not coming for any other branch.
The special thing about this branch is that it is created from the previous commit of another branch.

My config file looks like:

[core]
    repositoryformatversion = 0
    filemode = false
    bare = false
    logallrefupdates = true
    symlinks = false
    ignorecase = true
    hideDotFiles = dotGitOnly
[remote "origin"]
    url = <url here>
    fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
    remote = origin
    merge = refs/heads/master
[branch "new-develop"]
    remote = origin
    merge = refs/heads/new-develop
[branch "feature/Sprint4/ABC-123-Branch"]
    remote = origin
    merge = refs/heads/feature/Sprint4/ABC-123-Branch

This problem can happen when the remote branch has been deleted. Double check if it's really there. — Benny Neugebauer, Jan 18 '17 at 11:28
Future readers: If you know the remote branch exists, check if you are ignoring case or not. I had setup a local branch to track a remote branch, but typed the remote's name in all lower case letters. Just had to reconfigure local to track origin/BranchName instead of origin/branchname — Jerreck, Jun 27 '17 at 19:40
I just had this error and the problem was much simpler than the answers below, I'd lost my VPN connection. So this is also the error you get if git can't access the remote origin server. — Ben Thurley, Mar 18 '20 at 16:38
With solutions involving pruning the local branches to match the remote, first make sure you are not actually *on* the deleted branch locally, and especially that you don't have uncommitted changes on that branch. — M Katz, Jun 04 '21 at 08:35
There are excellent answers provided, so no need to add any new answers. But my 2 cents, when i get this message it means that the origin branch has been deleted, usually because it was deleted when it was merged into another branch. This is a common practice to keep the origin repo free of clutter from old branches. — angryITguy, Sep 29 '21 at 04:59
This just happened to me, Github deleted my branch on merge (this merge was done using the website, while I usually use the gh command-line program), it is as @BennyNeugebauer points out, make sure the branch is not deleted on remote. — Corfucinas, Feb 04 '22 at 13:25

torek · Accepted Answer · 2022-03-02T19:38:30.273

What this means

Your upstream—the remote you call origin—no longer has, or maybe never had (it's impossible to tell from this information alone) a branch named feature/Sprint4/ABC-123-Branch. There's one particularly common reason for that: someone (probably not you, or you'd remember) deleted the branch in that other Git repository.

What to do

This depends on what you want. See the discussion section below. You can:

create or re-create the branch on the remote, or
delete your local branch, or
anything else you can think of.

Discussion

You must be running git pull (if you were running git merge you would get a different error message or no error message at all).

When you run git fetch, your Git contacts another Git, based on the url line under the [remote "origin"] section of your configuration. That Git runs a command (upload-pack) that, among other things, sends your Git a list of all branches. You can use git ls-remote to see how this works (try it, it is educational). Here is a snippet of what I get when running this on a Git repository for git itself:

$ git ls-remote origin
From [url]
bbc61680168542cf6fd3ae637bde395c73b76f0f    HEAD
60115f54bda3a127ed3cc8ffc6ab6c771cbceb1b    refs/heads/maint
bbc61680168542cf6fd3ae637bde395c73b76f0f    refs/heads/master
5ace31314f460db9aef2f1e2e1bd58016b1541f1    refs/heads/next
9e085c5399f8c1883cc8cdf175b107a4959d8fa6    refs/heads/pu
dd9985bd6dca5602cb461c4b4987466fa2f31638    refs/heads/todo
[snip]

The refs/heads/ entries list all of the branches that exist on the remote,¹ along with the corresponding commit IDs (for refs/tags/ entries the IDs may point to tag objects rather than commits).

Your Git takes each of these branch names and changes it according to the fetch line(s) in that same remote section. In this case, your Git replaces refs/heads/master with refs/remotes/origin/master, for instance. Your Git does this with every branch name that comes across.

It also records the original names in the special file FETCH_HEAD (you can see this file if you peek into your own .git directory). This file saves the fetched names and IDs.

The git pull command is meant as a convenience short-cut: it runs git fetch on the appropriate remote, and then git merge (or, if so instructed, git rebase) with whatever arguments are needed to merge (or rebase) as directed by the [branch ...] section. In this case, your [branch "feature/Sprint4/ABC-123-Branch"] section says to fetch from origin, then merge with whatever ID was found under the name refs/heads/feature/Sprint4/ABC-123-Branch.

Since nothing was found under that name, git pull complains and stops.

If you run this as two separate steps, git fetch and then git merge (or git rebase), your Git would look at your cached remotes/origin/ remote-tracking branches to see what to merge with or rebase onto. If there was such a branch at one time, you may still have the remote-tracking branch. In this case, you would not get an error message. If there was never such a branch, or if you have run git fetch with --prune (which removes dead remote-tracking branches), so that you have no corresponding remote-tracking branch, you would get a complaint, but it would refer to origin/feature/Sprint4/ABC-123-Branch instead.

In either case, we can conclude that feature/Sprint4/ABC-123-Branch does not exist now on the remote named origin.

It probably did exist at one time, and you probably created your local branch from the remote-tracking branch. If so, you probably still have the remote-tracking branch. You might investigate to see who removed the branch from the remote, and why, or you might just push something to re-create it, or delete your remote-tracking branch and/or your local branch.

¹Well, all that it is going to admit to, at least. But unless they have specifically hidden some refs, the list includes everything.

Edit, Jul 2020: There's a new fetch protocol that can avoid listing everything, and only list names that your Git says it's looking for. This can help with repositories that have huge numbers of branches and/or tags. However, if your Git is interested in all possible names, you'll still get all the names here.

Thanks for explaining what the git pull command actually does. I was able to fix my issue by running git fetch and then merge. — fizch, Dec 04 '17 at 14:37
To remove non-existent remote branch references in your local repository, use `git remote prune origin` — Yoav, Jun 21 '18 at 14:54
@Ben-Uri: yes, or, run `git fetch --prune origin`, or set `fetch.prune` to `true` in your configuration (all three are intended to do the same thing, although in a few versions of Git some of these were not quite reliable). — torek, Jun 21 '18 at 15:13
You'd need to `git checkout ` and all be good (in some cases). — Alexander Shtang, Jul 29 '19 at 18:33
Wow... So weird. This only happens to me when connecting to BitBucket. :( — Will Strohl, Oct 10 '19 at 22:15
@WillStrohl: to see what branches the Git at Bitbucket actually has, use `git ls-remote `. Your current branch has, as its upstream, a branch name that does not exist in that Git at Bitbucket. How you got there, and what to do about it, is in the answer above. — torek, Oct 10 '19 at 22:24
The problem for me was that I deleted a development branch on Github without ever merging it (I abandoned the change). I got the same error message as the original poster. The solution for me was to delete my _local_ `master` branch and re-create it. — Jonathan Benn, Mar 09 '20 at 14:33
@JonathanBenn: you can use `git branch --set-upstream-to=origin/master master` to switch the upstream setting for your local `master`. Delete-and-recreate has that as a side effect (assuming you use the DWIM-style `git checkout master` to create it), with an additional side effect of forcing your `master` to match your `origin/master`. — torek, Mar 09 '20 at 17:57
@torek thanks, my Git-fu was not up to the task on this one. I'll keep in mind your recommendation for next time. I must have created a new local branch based on the deleted remote one, and then renamed my local branch to `master`. — Jonathan Benn, Mar 11 '20 at 12:23
argh! I ran into this. A github project renamed the master branch main! — codeDr, Jul 12 '20 at 13:38
Merging my staging to main branch - pull request completion deleted my branch. Couldn't find staging later on. Thanks for explaining the options. — sbsatter, Sep 30 '21 at 06:35
@sbsatter: pull requests are outside of Git (Git has no pull requests). GitHub's PR protocol allows you to semi-automatically delete the GitHub branch once the PR is merged. Other hosting sites may have similar features. — torek, Sep 30 '21 at 06:38

score 139 · Answer 2 · edited May 17 '22 at 23:35

139

This can also happen if you/someone renamed the branch. So follow these steps (if you know that branch name is renamed) Assuming earlier branch name as wrong-branch-name and someone renamed it to correct-branch-name So.

git checkout correct-branch-name

git pull (you'll see this "Your configuration specifies..")

git branch --unset-upstream

git branch --set-upstream-to=origin/correct-branch-name

for older git versions git push --set-upstream origin correct-branch-name

git pull (you'll not get the earlier message )

edited May 17 '22 at 23:35

dan carter

3,859
1
30
31

answered Jan 04 '18 at 16:57

Extreme

2,211
1
15
25

2

It's not even necessary to `git push` and it won't work if the current branch is behind its remote. `git pull origin correct-branch-name` is enough. – Pierre Nov 08 '18 at 11:00
10

The command to set upstream is wrong above. Do a git pull after, --unset-upstream operation, in the output of the pull you can see a error, with the command to set the upstream, like below, git branch --set-upstream-to=origin/ mybranch – Ankit Marothi Oct 03 '19 at 11:15
Worked nicely for me after removing some large files from my repo and needed to push back to a new repo i just created – Akah Dec 14 '19 at 19:20
5

For anyone visiting this more recently: '--set-upstream' is no longer supported. Now you should use "git branch --set-upstream-to=origin/ main" – Josh Bone Jan 28 '21 at 20:03
1

The only answer that worked – poitroae Nov 03 '21 at 14:53

Malhaar Punjabi · Answer 3 · 2017-11-07T23:01:55.200

50

Check if your remote branch is available to pull. I had the same issue, finally realized the remote branch was deleted by someone.

edited Nov 07 '17 at 23:01

answered Oct 19 '17 at 22:20

Malhaar Punjabi

645
7
9

5

It was the same for me! – aerin Mar 03 '18 at 00:17
6

After a pull request, the merger (i.e. the person who did the merge) has the option to delete the branch that was merged into the target branch. If you try to pull at that point you'll get this error. – Artokun Oct 01 '18 at 19:48
that is true :) – Malhaar Punjabi Mar 05 '19 at 00:39

score 24 · Answer 4 · answered Jul 20 '20 at 18:27

This is a more common error now as many projects are moving their master branch to another name like main, primary, default, root, reference, latest, etc, as discussed at Github plans to replace racially insensitive terms like ‘master’ and ‘whitelist’.

To fix it, first find out what the project is now using, which you can find via their github, gitlab or other git server.

Then do this to capture the current configuration:

$ git branch -vv
...
* master  968695b [origin/master] Track which contest a ballot was sampled for (#629)
...

Find the line describing the master branch, and note whether the remote repo is called origin, upstream or whatever.

Then using that information, change the branch name to the new one, e.g. if it says you're currently tracking origin/master, substitute main:

git branch master --set-upstream-to origin/main

You can also rename your own branch to avoid future confusion:

git branch -m main

thanks for catch! This main master thing is only getting more frustration. — Abbas Elmas, Feb 18 '21 at 15:31
Or `git fetch upstream`, `git checkout main`, then next time `git pull`. — gerrit, Apr 16 '21 at 13:36

score 15 · Answer 5 · answered Oct 16 '17 at 18:33

15

For me it was a case sensitivity issue. My local branch was Version_feature2 instead of Version_Feature2. I re-checked out my branch using the correct casing and then git pull worked.

answered Oct 16 '17 at 18:33

nicko

440
3
10

2

This turned out to be my problem too. It's not necessary obvious with fairly long/complicated branch names. – Håkon K. Olafsen Sep 03 '19 at 07:14
This was the issue for me as well – Vicky Singh Sep 20 '21 at 09:19
My case was very sensitive too! – Krafty Dec 13 '21 at 23:21

score 8 · Answer 6 · answered Jan 03 '20 at 11:33

8

You can easily link your local branch with remote one by running:

git checkout <your-local-branch>
git branch --set-upstream-to=origin/<correct-remote-branch> <your-local-branch>
git pull

answered Jan 03 '20 at 11:33

Gendos-ua

333
3
8

score 7 · Answer 7 · answered Feb 12 '17 at 16:39

7

I got a similar error when the actual cause was that my disk was full. After deleting some files, git pull began to work as I expected.

answered Feb 12 '17 at 16:39

user1747134

2,232
18
23

Same here - I guess git tries to fetch something from the remote, silently fails to write it because the disk is full, and then doesn't find the files and complains that the "ref wasn't fetched"? – rob74 Feb 04 '21 at 12:25

score 7 · Answer 8 · edited May 10 '18 at 15:55

7

In my case I was simply lacking of initial commit on remote branch, so local branch wasn't finding anything to pull and it was giving that error message.

I did:

git commit -m 'first commit' // on remote branch
git pull // on local branch

edited May 10 '18 at 15:55

THE JOATMON

16,761
34
110
200

answered Apr 21 '17 at 08:28

Nicola Gallazzi

6,536
5
35
52

score 6 · Answer 9 · edited Nov 28 '17 at 10:08

6

This error can also be received when the origin branch name has some case issue.

For example: origin branch is team1-Team and the local branch has been checkout as team1-team. Then, this T in -Team and t in -team can cause such error. This happened in my case. So, by changing the local name with the origin branch's name, the error was solved.

edited Nov 28 '17 at 10:08

Xpleria

4,994
5
50
60

answered Nov 28 '17 at 09:08

akgupta

91
1
6

score 5 · Answer 10 · answered Jan 08 '22 at 16:40

I've found this error occurs frequently when pulling updates from a repo whose default master branch has been renamed to main. Encountered this a lot after the 2020 trend of renaming master branch to main branch.

So if you had previously cloned a repo with the default master branch and that branch has since been renamed to main, one way to fix is by simply pointing your upstream from master to main:

git branch --set-upstream-to=origin/main master

If that command succeeds, you should see a message like this:

Branch 'master' set up to track remote branch 'main' from 'origin'.

You can then rename your local branch from master to main (to keep consistent with the remote branch name) with git branch -m master main

score 3 · Answer 11 · answered Mar 18 '19 at 18:05

3

I kept running into this issue. In my case, @Jerreck's comment about case differences in the branch names was the cause of this error. Some Windows tools aren't aware of case sensitivity.

To turn off case-sensitivity in git, run this command:

git config --global core.ignorecase true

Note that this will impact more than branch names. For example, if you have "Foo.h" and "foo.h" in the same directory (not a great idea when building software for Windows) then I suspect you cannot turn off case sensitivity.

answered Mar 18 '19 at 18:05

Stéphane

18,697
23
86
128

1

This doesn't help with the issue because `core.ignorecase` option only affects your files but not git internal files (which resides in `.git` folder) – Lu55 Nov 11 '20 at 03:12
`core.ignorecase true` does not work for me (the problem was a case difference in the branch name). So I've just set upstream to the correct branch name – oleksa Feb 05 '21 at 09:53

CodeChari · Answer 12 · 2021-09-22T03:14:52.877

3

Check for case sensitivity

In my case, my branch name (remote) had uppercase letters, for example: BranchName. Accidently, I created a branch branchname (all lower case) on my local machine and set upstream to the same, and this error appeared.

Solution: I deleted the local repository, cloned it again, and checked out to BranchName

edited Sep 22 '21 at 03:14

answered Jun 17 '21 at 15:50

CodeChari

195
1
4
18

score 2 · Answer 13 · answered Jun 30 '19 at 11:34

In my case, i had deleted the original branch from which my current branch derived from. So in the .git/config file i had:

[branch "simil2.1.12"]
    remote = origin
    merge = refs/heads/simil2.0.5
    rebase = false

the simil2.0.5 was deleted. I replaced it with the same branch name:

[branch "simil2.1.12"]
    remote = origin
    merge = refs/heads/simil2.1.12
    rebase = false

and it worked

score 2 · Answer 14 · answered Apr 03 '21 at 11:20

In my case, I renamed the branch on Github which in return told me to execute the following commands:

The default branch has been renamed!

main is now named <new_name>

If you have a local clone, you can update it by running:

git branch -m main <new_name>
git fetch origin
git branch -u origin/<new_name> <new_name>
git remote set-head origin -a

score 2 · Answer 15 · answered Apr 06 '21 at 08:31

I had a similar issue with master/main branch. In my case I did not have enough free space on my harddisk. After freeing up some space, it worked.

I assume its because the files /.git needs some space to edit its file. For example the file: 'refs/heads/feature/Sprint4/ABC-123-Branch'

score 1 · Answer 16 · answered Sep 23 '17 at 05:47

For me this happened because i merged a branch dev into master using web interface and then tried to sync/pull using VSCode which was open on dev branch.(its weird that i could not change to master without getting this error.)

git pull
Your configuration specifies to merge with the ref 'refs/heads/dev'
from the remote, but no such ref was fetched.'

It makes sense that is not finding it refs/heads/dev - for me it was easier to just delete the local folder and clone again.

AB Abhi · Answer 17 · 2018-11-01T10:24:48.107

1

Just check if someone deleted the branch at remote.

edited Nov 01 '18 at 10:24

answered Nov 01 '18 at 05:30

AB Abhi

2,476
22
30

score 1 · Answer 18 · answered Nov 07 '19 at 09:54

I just got the same error, when I didn't use the correct case. I could checkout out 'integration'. Git told me to perform a git pull to update my branch. I did that, but received the mentioned error. The correct branch name is 'Integration' with a capital 'I'. When I checked out that branch and pulled, it worked without problem.

score 1 · Answer 19 · answered Aug 31 '21 at 03:18

1

Rename the local branch

git branch -m temp

Display all branches

git branch -a

Check out the specific remote branch

git checkout main

Delete the temp branch

git branch -d temp

answered Aug 31 '21 at 03:18

Michael

375
4
15

score 0 · Answer 20 · answered Jan 10 '19 at 12:19

0

I just got exactly this error when doing "git pull" when my disk was full. Created some space and it all started working fine again.

answered Jan 10 '19 at 12:19

user7550381

1

score 0 · Answer 21 · answered Jan 30 '19 at 11:38

0

You can edit the ~/.gitconfig file in your home folder. This is where all --global settings are saved.

Or, use git config --global --unset-all remote.origin.url and after run git fetch with repository url.

answered Jan 30 '19 at 11:38

Angelo Mendes

747
10
21

score 0 · Answer 22 · answered Mar 29 '19 at 14:09

I was facing the same issue where my current branch was dev and I was checking out to MR branch and doing git pull thereafter. An easy workaround that I took was I created a new folder for MR Branch and did git pull there followed by git clone.

So basically I maintained different folders for pushing code to different branch.

score 0 · Answer 23 · answered Jun 17 '21 at 18:25

In my case the master cannot be fetched in a new project.

And it worked after I put this in the command line,

git config --global http.sslVerify false

ref: https://confluence.atlassian.com/bitbucketserverkb/can-t-access-bitbucket-server-with-git-issuer-certificate-is-invalid-779171808.html

score 0 · Answer 24 · answered Dec 13 '21 at 14:47

0

The branch's pull request in the Github repo was approved, it was merged into the dev branch and doesn't exist on origin any more.

answered Dec 13 '21 at 14:47

Andrew Koper

5,068
5
37
47

score 0 · Answer 25 · answered Dec 14 '21 at 14:51

0

In my case the repo was temporary unavailable (under maintenance).

answered Dec 14 '21 at 14:51

IKo

3,761
6
26
49

score 0 · Answer 26 · answered Dec 28 '21 at 17:10

I have gotten this exact error, but none of the suggested answers (possibly the case sensitivity) was the issue. They probably are for 99% of the issues out there, but that still leaves 1%.

It turned out, mixing WSL / Linux file shares and Windows base directories was the problem. I was running WSL (Ubuntu 20.04) and has a repo that was accessed / edited from Windows, but the code was running on WSL. I may have done some git status checks from the WSL side.

The repo existed, the case was correct, the internet worked fine, none of the branches were removed, etc. Yet I also got the error Your configuration specifies to merge with the from the remote, but no such ref was fetched.?

What my fix was, was to make sure all of the items were pushed / all changes recorded, then I just removed the directory and did a 'git clone' again from Windows. Then the 'git checkout' worked fine. I realize this isn't really an answer, but it did work.

I was doing Linux development where a code library automates certain operations, including 'git clone'; however, I normally do my code pushes from Windows. My guess is that the .git folder is not cross-platform compatible (not that I had any expectation it was). Yet, it usually works. Is it a bug? Debateable.

git will also occasionally try too hard to be nice and munge line endings; that's a different problem (and bordering on religion. I'm an Agnostic. Yes, there's a setting.)

score 0 · Answer 27 · answered Mar 04 '22 at 08:47

Happened to me when installing packages with yarn. An own dependency had a renaming of branch main into master. Only updating upstream on the dependency did not fix it, I additionally had to clean the yarn cache.

Project A renamed the main branch (main -> master). Project A is a dependency of Project B.
yarn install on Project B <-- causes error
Push updated upstream on Project A
yarn install on Project B <-- causes error
yarn cache clean
yarn install on Project B <-- works now

score -2 · Answer 28 · answered Aug 04 '17 at 16:49

-2

If another pull just works, it means your internet wasn't connected.

answered Aug 04 '17 at 16:49

Pyrolistical

26,934
21
79
105

2

A number of downvotes and yet this was the cause I had of receiving this error. I had Internet but had lost the VPN to my git server. After reconnecting to the VPN the pull worked fine. – Ben Thurley Mar 18 '20 at 16:41

Your configuration specifies to merge with the from the remote, but no such ref was fetched.?

28 Answers28

What this means

What to do

Discussion

Check for case sensitivity

Linked