Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show branches list in "git pull from" #39216

Merged
merged 4 commits into from
Dec 15, 2017
Merged

Conversation

Dozed12
Copy link
Contributor

@Dozed12 Dozed12 commented Nov 27, 2017

As requested in #37490

From what I tested and the git output it should be working like before but with the new requested feature so hopefully it's good.

@joaomoreno joaomoreno added this to the Backlog milestone Nov 28, 2017
@joaomoreno joaomoreno added the git GIT issues label Nov 28, 2017
@Dozed12 Dozed12 force-pushed the master branch 2 times, most recently from e81ed33 to f0e2c7d Compare November 28, 2017 23:45
@joaomoreno joaomoreno merged commit bed86d2 into microsoft:master Dec 15, 2017
@joaomoreno joaomoreno modified the milestones: Backlog, December 2017/January 2018 Dec 15, 2017
@joaomoreno
Copy link
Member

Thanks! 🍻

@eladcandroid
Copy link

Can you insert this update into 1.19.x version please?

@joaomoreno
Copy link
Member

No, it will appear first in 1.20.

@arcotek-ltd
Copy link

And you've regressed it in 1.28.2?

image

The branch I have created is not in the list, however it is there in Sourcetree.

@gregdelozier
Copy link

This is a late comment, I know, but it seems like this functionality isn't working correctly as of 2/2020 -- we have consistently created branches in ADO Git, and we can't see them in VSCode until we either do Git:Fetch (see issue 52571 where that's advised) or we do a $ git pull from the command line.

It seems that pull from only sees the branches that the current local copy of the repo knows about, and the only ways to refresh that list are the Git:Fetch and command line $ git pull options.

It would be nice for pull from to refresh that list first, if possible. If speed is a concern, then some other method of forcing a refresh from the command line would be helpful.

@gregdelozier
Copy link

gregdelozier commented Feb 10, 2020

For what it's worth, this preference option
[ ] Fetch all branches when pulling or just the current one
...appears to be broken. It generates the command "git pull -tags" which results in this error:

git pull --tags
Fetching tags only, you probably meant:
git fetch --tags

@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
git GIT issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants