Today I had some time at hand, and I confirmed that the option is the cause by reading the git-clone(1) manpage, it notes that:Ĭreate a shallow clone with a history truncated to the specified number of commits. I reflected why it happened after work, the only difference I can remember was that I clone that repo with the option -depth, that is, it was a shallow clone to save some disk space. Git Fetch only downloads the new commits in a separate branch without. It worked after I changed it to +refs/heads/*:refs/remotes/origin/*. Git Fetch is a very commonly used command to communicate with the remote repository. Note that git branch -a includes git branch -r, but adds the word remotes/ in front of the origin/master names.
It never happens before, and it happened when I was in a rush to rebase my code, as someone in my team pushed his code.Īfter searching, it seemed that the configuration of fetch of that repo was different(this Stack Overflow thread for example) than before, it was specified that only master can be fetched. Running git branch -r will list your remote-tracking names, so git branch -r shows you what your Git saw in their Git, the last time your Git updated using their Git. The fetched commits are saved as remote branches. Last week I came into a problem with Git, that I can't fetch the remote branch that I just pushed to. To clone a branch without fetching other branches, you can use the git-remote add command with git-fetch. When we use the git fetch commands we fetch the commits of a remote repository into our local repository.
0 kommentar(er)
