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

Why %(upstream:track)? ... I'm intrigued! 😀 #21

Open
pvdb opened this issue Jun 24, 2019 · 0 comments
Open

Why %(upstream:track)? ... I'm intrigued! 😀 #21

pvdb opened this issue Jun 24, 2019 · 0 comments

Comments

@pvdb
Copy link

pvdb commented Jun 24, 2019

It's not wrong, but I was just wondering about the purpose of this line:

%(color:bold yellow)%(upstream:track)%(color:reset)

The %(upstream:track) directive is only relevant if you have two local branches, one of which is the upstream for the other one... put differently: it has no relevance for remote-tracking branches.

Like I said: nothing wrong with it, but I'm intrigued by the workflow where you have a local branch with an upstream local... ie. what kind of git workflow would give rise to this use-case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant