Git: Cannot see new remote branch

Question

A colleague pushed a new remote branch to origin/dev/homepage and I cannot see it when I run:

$ git branch -r

I still see preexisting remote branches.

I assume this is because my local remote refs are not up-to-date hence when I ran a git pull nothing happened since git pull only pulls on the current working branch correct? Unlike git push which pushes all branches that have changes to the corresponding remote branch?

A related problem - [Can't see remote branch](https://stackoverflow.com/q/12730344/465053) — RBT, Apr 04 '18 at 06:20
In my case `git fetch ` did the trick. Without the name of the remote, it did NOT work. — Menno Deij - van Rijswijk, Jul 13 '20 at 09:17

Marco Leogrande · Accepted Answer · 2012-10-06T20:57:29.203

241

First, double check that the branch has been actually pushed remotely, by using the command git ls-remote origin. If the new branch appears in the output, try and give the command git fetch: it should download the branch references from the remote repository.

If your remote branch still does not appear, double check (in the ls-remote output) what is the branch name on the remote and, specifically, if it begins with refs/heads/. This is because, by default, the value of remote.<name>.fetch is:

+refs/heads/*:refs/remotes/origin/*

so that only the remote references whose name starts with refs/heads/ will be mapped locally as remote-tracking references under refs/remotes/origin/ (i.e., they will become remote-tracking branches)

edited Oct 06 '12 at 20:57

answered Oct 06 '12 at 19:08

Marco Leogrande

8,050
4
30
48

6

I was able to see the new remote branch after doing a git fetch origin, but not sure what the difference is if I just did a git fetch? I read about git remote update, but wasn't clear what that would have done. Would I need to run git fetch for any new remote branches from here on out? – hybrid9 Oct 07 '12 at 01:07
1

@hybrid9 If you use `git fetch`, git will download the references from the default remote repository that has been specified in `.git/config`: usually it will be called `origin`, so both commands are equivalent, but your specific configuration might be different for some reason. No, you don't need to give `git fetch` for every branch, as (by default) it fetches **all** branches. – Marco Leogrande Oct 07 '12 at 01:19
My git is the default no changes to my config. Sorry, I meant if a new remote branch is added by someone that I need to work in, I would need to run git fetch origin again before i can track it? I worry about what git fetch will do to my other remotely tracked branches like develop and master when I'm still doing work in them. Guess I should pull on those before I fetch? – hybrid9 Oct 07 '12 at 02:38
1

@hybrid9 `git pull` is equivalent to `git fetch` + `git merge` (or `git rebase` if you have changed defaults), so you can keep using `git pull` as usual, and the new remote branches will pop up by themselves. – Marco Leogrande Oct 07 '12 at 05:07
1

I originally ran git pull but i never saw that new remote branch which really confused me. Only until i ran git fetch origin. I appreciate the time in answering my questions. – hybrid9 Oct 07 '12 at 11:31
3

@hybrid I have the same issue. `git ls-remote gerritrepo:project` shows the new remote branch but `git branch -a` does not...I have to make another clone and only then the new branch will appear – Vikram Jul 09 '13 at 18:41
Thanks for the info! I didn't know about the `ls-remote` option! +1! – rmbianchi Jun 19 '19 at 11:49
@MarcoLeogrande +1 – devio Jul 31 '19 at 14:16
Thanks for your answer! I had this problem and somehow in my .git/config I had changed the * values for develop, so only develop branches where shown, and the rest were hidden. – mcabreb Nov 26 '19 at 14:24
I also had to explicitly use git fetch origin to see the branch with `git branch -a`, not sure why though – L H Jul 14 '20 at 00:29
git fetch worked like charm!! – David Castro Oct 04 '21 at 21:57
1

My issue was that my .git/conf contained `+refs/heads/master:refs/remotes/origin/master`. I Replaced `master` with `*` as suggested here and now I can fetch new branches. In my case I think I had done a shallow copy during the initial `git clone` a long time ago and forgot about it. – Alex Telon Feb 03 '22 at 19:40
problem disappeared after closing and opening the git command line window, which is in my case was "MINGW64". – Peter Mar 02 '22 at 17:07
Why not `git branch -r` to confirm remote branch name exists followed `git checkout -b origin/` to check it out against a local branch name? – myusrn Aug 27 '22 at 23:01

score 155 · Answer 2 · answered Sep 06 '17 at 17:26

155

Check whether .git/config contains

[remote "origin"]
    url = …
    fetch = +refs/heads/master:refs/remotes/origin/master

If so, change it to say

[remote "origin"]
    url = …
    fetch = +refs/heads/*:refs/remotes/origin/*

Then you should be able to use it:

$ git fetch
remote: Counting objects: …
remote: Compressing objects: ..
Unpacking objects: …
remote: …
From …
 * [new branch]            branchname -> origin/branchname
$ git checkout branchname
Branch branchname set up to track remote branch branchname from origin.
Switched to a new branch 'branchname'

answered Sep 06 '17 at 17:26

Jesse Glick

24,539
10
90
112

24

This happened to me after an initial shallow clone. – ArkTekniK Aug 17 '18 at 14:24
Perfect!!! Thanks a lot! That happened to me when installing a custom Homebrew tap with the command `brew tap user/repo`: the local copy of the repo cloned by `brew` had the settings you mentioned and it was not possible to see and use the other branches I had in my repo. Thanks again! :) +1! – rmbianchi Jun 19 '19 at 11:48
11

The following command can be used instead of manual editing the _.git/config_ file. `git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"` and then `git fetch origin` to get all branches on _origin_. – dotnetCarpenter Jan 07 '20 at 14:00
1

this is a nice one! – madz May 01 '20 at 11:13
2

I was facing this issue and the first answer didn't help me, but yours did. The reason, I think might be, that I have cloned only a single branch from the remote. – arsdever Nov 18 '20 at 12:31
happened to me when I cloned my repo as bare using TortiseGit – matt Jan 14 '21 at 02:13
or if it missing all together :P – CervEd Jun 10 '21 at 09:47
My older git repositories have this corrupted state, newer ones do not. The only differences I can see are: created in older versions of git (is git so awful that it isn't forwards compatible?), and ... the newer ones have been accessed by the GitHubDesktop app (is Github.com corrupting them?) – Adam Mar 14 '22 at 15:25
omg i spent an hour troubleshooting, this worked for me finally, thank you! – Noon Time Sep 20 '22 at 19:56

Jacek Dziurdzikowski · Answer 3 · 2020-01-17T16:27:45.550

109

The simplest answer is:

git fetch origin <branch_name>

edited Jan 17 '20 at 16:27

answered Mar 28 '18 at 14:24

Jacek Dziurdzikowski

2,015
2
13
20

12

This was literally the ONLY thing that worked for me. – Theodore R. Smith Jun 13 '18 at 19:15
6

It doesn't work for me. I get this error: `fatal: Couldn't find remote ref ` – Parisa Khateri Sep 18 '18 at 08:07
5

yes it did work for me as well, after this git checkout worked fine !! – whoami - fakeFaceTrueSoul Mar 26 '19 at 20:08
And this is an actual answer..... :) – jtlz2 Feb 24 '22 at 07:36
A thousand upvotes to this. – Abhimanyu Shekhawat Apr 12 '23 at 12:46
Even after this I cannot checkout the branch :( – Jagruti Jun 22 '23 at 06:57

score 68 · Answer 4 · edited Jun 04 '21 at 06:11

Let's say we are searching for release/1.0.5

When git fetch --all is not working and that you cannot see the remote branch and git branch -r not show this specific branch.

1. Print all refs from remote (branches, tags, ...):

git ls-remote origin Should show you remote branch you are searching for.

e51c80fc0e03abeb2379327d85ceca3ca7bc3ee5        refs/heads/fix/PROJECT-352
179b545ac9dab49f85cecb5aca0d85cec8fb152d        refs/heads/fix/PROJECT-5
e850a29846ee1ecc9561f7717205c5f2d78a992b        refs/heads/master
ab4539faa42777bf98fb8785cec654f46f858d2a        refs/heads/release/1.0.5
dee135fb65685cec287c99b9d195d92441a60c2d        refs/heads/release/1.0.4
36e385cec9b639560d1d8b093034ed16a402c855        refs/heads/release/1.0
d80c1a52012985cec2f191a660341d8b7dd91deb        refs/tags/v1.0

The new branch release/1.0.5 appears in the output.

2. Force fetching a remote branch:

git fetch origin <name_branch>:<name_branch>

$ git fetch origin release/1.0.5:release/1.0.5

remote: Enumerating objects: 385, done.
remote: Counting objects: 100% (313/313), done.
remote: Compressing objects: 100% (160/160), done.

Receiving objects: 100% (231/231), 21.02 KiB | 1.05 MiB/s, done.
Resolving deltas: 100% (98/98), completed with 42 local objects.
From http://git.repo:8080/projects/projectX
 * [new branch]        release/1.0.5 -> release/1.0.5

Now you have also the refs locally, you can checkout (or whatever) this branch.

Job done!

#2 worked for me, but I had to do it everytime I needed to fetch a remote branch. Updating the git config was the definitive fix for me. — RotS, Dec 11 '20 at 09:35
Faced the same issue on the old repository. Deleting and downloading the repository again helped. — cosic, Feb 19 '21 at 20:49
Why not `git branch -r` to confirm remote branch name exists followed `git checkout -b origin/` to check it out against a local branch name? — myusrn, Aug 27 '22 at 23:01

score 34 · Answer 5 · answered Jun 26 '13 at 20:05

34

Doing a git remote update will also update the list of branches available from the remote repository.

If you are using TortoiseGit, as of version 1.8.3.0, you can do "Git -> Sync" and there will be a "Remote Update" button in the lower left of the window that appears. Click that. Then you should be able to do "Git -> Switch/Checkout" and have the new remote branch appear in the dropdown of branches you can select.

answered Jun 26 '13 at 20:05

metaforge

911
10
11

21

`git remote update` is an old way to do this, the newer preferred command is `git fetch`. – May 29 '14 at 20:41
1

In my version of TortoiseGit (2.8.0.0) the button in the lower left has multiple options under the arrow, and it remembers what you selected previously. This means the button might not say "Remote Update". If you haven't used it before it will say "Pull". So click on the arrow and you will see "Remote Update" in the list of options. – Michael Hinds Nov 30 '19 at 16:05

score 6 · Answer 6 · answered Oct 23 '17 at 22:21

6

It sounds trivial, but my issue was that I wasn't in the right project. Make sure you are in the project you expect to be in; otherwise, you won't be able to pull down the correct branches.

answered Oct 23 '17 at 22:21

BlackHatSamurai

23,275
22
95
156

score 6 · Answer 7 · answered Mar 06 '19 at 11:38

6

I used brute force and removed the remote and then added it

git remote rm <remote>
git remote add <url or ssh>

answered Mar 06 '19 at 11:38

Rubber Duck

3,673
3
40
59

score 4 · Answer 8 · answered May 05 '17 at 03:55

4

What ended up finally working for me was to add the remote repository name to the git fetch command, like this:

git fetch core

Now you can see all of them like this:

git branch --all

answered May 05 '17 at 03:55

Serj Sagan

28,927
17
154
183

score 0 · Answer 9 · answered Jan 16 '20 at 14:20

0

You can checkout remote branch /n git fetch && git checkout remotebranch

answered Jan 16 '20 at 14:20

thao vu

26
2

Git: Cannot see new remote branch

9 Answers9

Linked