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

2.49 Pushing to a different remote wrongly ask about new branch #3427

Closed
Kryptos-FR opened this issue Nov 21, 2016 · 3 comments
Closed

2.49 Pushing to a different remote wrongly ask about new branch #3427

Kryptos-FR opened this issue Nov 21, 2016 · 3 comments
Milestone

Comments

@Kryptos-FR
Copy link

Kryptos-FR commented Nov 21, 2016

Since 2.49, pushing to a different remote always ask to create the branch even though it does exist on the remote. This is a bit annoying that pushing cannot be done with a few clicks anymore.

image

Here is a summary of my git environment if that can help:

$ git lfs env
git-lfs/1.5.0 (GitHub; windows amd64; go 1.7.3; git 13fda8da)
git version 2.10.2.windows.1
@EbenZhang
Copy link
Contributor

EbenZhang commented Dec 20, 2016

Probably introduced in #3403 #3291

did some investigation, seems from here: 75364f2

@EbenZhang
Copy link
Contributor

EbenZhang commented Dec 20, 2016

@jbialobr any reason in 75364f2 the Module.GetRefs(tags: true, branches: true); got changed to Module.GetRefs(tags: false, branches: true).
The former one returns only local branches whereas the latter one returns tags, local branches and remote branches (the parameter names of GetRefs ars misleading).

@jbialobr
Copy link
Member

jbialobr commented Mar 3, 2017

Just did not need tags and got mislead...

@jbialobr jbialobr added this to the 2.49.1 milestone Mar 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants