git fetch doesn't fetch all branches

 

I have cloned a repository, after which somebody else has created a new branch, which I'd like to start working on. I read the manual, and it seems dead straight easy. Strangely it's not working, and all the posts I've found suggest I'm doing the right thing. So I'll subject myself to the lambasting, because there must be something obviously wrong with this:

The correct action seems to be 

git fetch
git branch -a
* master
  remotes/origin/HEAD --> origin/master
  remotes/origin/master
git checkout -b dev-gml origin/dev-gml

At this point there is a problem, for some reason after git fetch I can't see the dev-gml remote branch. Why not? If I clone the repository freshly, it's there, so certainly the remote branch exists: 

$ mkdir ../gitest
$ cd ../gitest
$ git clone https://github.com/example/proj.git
Cloning into proj...
remote: Counting objects: 1155, done.
remote: Compressing objects: 100% (383/383), done.
remote: Total 1155 (delta 741), reused 1155 (delta 741)
Receiving objects: 100% (1155/1155), 477.22 KiB | 877 KiB/s, done.
Resolving deltas: 100% (741/741), done.
$ cd projdir
$ git branch -a
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/dev-gml
  remotes/origin/master

I've tried git update , git pull , git fetch --all , git pretty-please in all possible permutations...

The problem can be seen when checking the remote.origin.fetch setting
(The lines starting with $ are bash prompts with the commands I typed. The other lines are the resulting output) 

$ git config --get remote.origin.fetch
+refs/heads/master:refs/remotes/origin/master

As you can see, in my case, the remote was set to fetch the master branch specifically and only. I fixed it as per below, including the second command to check the results. 

$ git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"
$ git config --get remote.origin.fetch
+refs/heads/*:refs/remotes/origin/*

The wildcard * of course means everything under that path.

Unfortunately I saw this comment after I had already dug through and found the answer by trial and error.

To track a (new) remote branch as a local branch: 

git checkout -b <local branch> <remote>/<remote branch>

or (sometimes it doesn't work without the extra remotes/ ): 

git checkout -b <local branch> remotes/<remote>/<remote branch>

Edit: You need to run git remote update or git remote update <remote> . Then you can run git branch -r to list the remote branches.

Helpful git cheatsheets

  • Git Cheat Sheet (My personal favorite)
  • Some notes on git
  • Git Cheat Sheet (pdf)

    • I had this issue today on a repo.

    It wasn't the +refs/heads/*:refs/remotes/origin/* issue as per top solution.

    Symptom was simply that git fetch origin or git fetch just didn't appear to do anything, although there were remote branches to fetch.

    After trying lots of things, I removed the origin remote, and recreated it. That seems to have fixed it. Don't know why.

    remove with: git remote rm origin

    and recreate with: git remote add origin <git uri>

    链接地址: http://www.djcxy.com/p/3838.html

    上一篇: 如何在Git中检出远程分支？

    下一篇: git fetch不会获取所有分支