What happens when git fetch cannot get a remote branch?

the problem shown in the figure when using git to go to a project on clone GitLab
clipboard.png
is solved by https://stackoverflow.com/que..

but there is a new problem.
under the project obtained through the above answer, through the git branch-a command, you can only see the master branch
other dev, test, etc.
use git fetch and git fetch-- all is useless or just see the master branch but not the other branches
at present
ask for support

Mar.14,2021

my problem is exactly the same as yours, including the problem at the beginning. The project on my side seems to be a bit large, so I can't CLONE it normally, so I use-- depth to pull part of it, which is the method in stackoverflow, but it can't display the remote branch. No matter what I do, it's useless. I guess the reason is that the remote branch is not all pulled down during CLONE, resulting in a problem with the remote branch. But being able to pull and push normally, this problem has been bothering me for a long time. I don't know if the subject has solved it or not. If you have solved it, tell me the solution. I feel that GIT has a lot of problems when it comes to pulling large items. It is more difficult to use


checkout directly than SVN


  • for the problem that you can't see the branches, you need to first git pull Synchronize the data of the server, and then git branch-a you can see all the branches.

Clone.

Menu