Published Git branch in DevOps Azure not showing up in VS2013 or Git command line

My colleague has a local branch. He "publishes" it from VS Team Explorer. It appears in the list of branches of Visual Studio Online.

I am connected to the same TFS-Git system registered through VS, connected via Team Explorer, and yet, when I look at the list of branches, I can clone from it, it’s not there.

I finally resorted to using the command line to view all branches, but it does not even appear there. Here is a screenshot:

enter image description here

What am I missing? This is a serious problem for us.

Thanks in advance.

UPDATE

I'm not sure I did it, but now I see a branch in Team Explorer. My best guess is that this is related to issuing a manual “sample” of the branches “master” and “development”. I am surprised that you will need to see the remote branches. Essentially, you need to extract and cache information about the remote branch, and then issue another command (branch -r) to see that you have cached. Perhaps this is not so, but this is my best guess. Hope this helps someone else.

+6
source share
1 answer

You need to do Pull first to make sure the local repo is updated with the changes. Then you have new reversal pointers \ otherdudes local.

Then you can create a new branch in the visual studio and select the branch origin \ otherdudes as the server target.

This is how git works, and the same actions from the command line will also do the same. You always need to create a working copy of the published branch before you can edit it.

+9
source

Source: https://habr.com/ru/post/976797/


All Articles