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.

Sign up for GitHub

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

Jump to bottom

Use upstream branch config to find remote branch #52

Closed
exalted opened this issue Aug 23, 2013 · 2 comments
Closed

Use upstream branch config to find remote branch #52

exalted opened this issue Aug 23, 2013 · 2 comments

Comments

@exalted
Copy link

exalted commented Aug 23, 2013

I guess git-up will look for a branch on remote with the same name of the currently checked–out local branch, instead of reading the tracking info (that is set with --set-upstream).
@aanand
Copy link
Owner

aanand commented Aug 27, 2013

Yes. This is because the upstream branch won't always be set (e.g. if the user hasn't pushed that branch before).

Perhaps it should check if an upstream is set first, and fall back to name matching if not. Pull requests welcome!

@exalted
Copy link
Author

exalted commented Aug 27, 2013

Yea, thanks. Don’t hold your breath though 😉

@msiemens msiemens mentioned this issue Oct 6, 2013
Closed
msiemens added a commit to msiemens/PyGitUp that referenced this issue Oct 7, 2013
@msiemens
Use tracking info instead of <remote>/<branch> (closes #6)
17b7314 
Instead of checking every local <branch>, if <remote>/<branch>
exists, we now use tracking information to find out, where to
pull the changes from. This closes #6 and also fixes
aanand/git-up#52.
@exalted exalted closed this as completed Feb 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aanand @exalted