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

feature request: push remote branch name #291

Closed
olets opened this issue Jan 6, 2022 · 5 comments
Closed

feature request: push remote branch name #291

olets opened this issue Jan 6, 2022 · 5 comments

Comments

@olets
Copy link

olets commented Jan 6, 2022

It'd be nice to have a VCS_STATUS_PUSH_REMOTE_BRANCH.

Guessing that between VCS_STATUS_PUSH_REMOTE_NAME, VCS_STATUS_REMOTE_NAME, and VCS_STATUS_REMOTE_BRANCH I could probably figure the patch… if I knew how to work in C++ 😄 But I don't so here I am.

@romkatv
Copy link
Owner

romkatv commented Jan 6, 2022

I wonder why I didn't add that in the first place.

Do you actually have a use case for it? Do you use different names for the local and the @{push} branch? Can you describe your workflow?

@olets
Copy link
Author

olets commented Jan 6, 2022

I don't have a real life workflow use case — I rarely work with multiple remotes, and when I do there's rarely a reason to change the branch names. Guess I can imagine doing it as a handy way to keep track of a branch's @{u} and @{push} if your prompt didn't surface that information. edit: thinking about it some more, I think I've done it a few times for that reason. But very rarely

I noticed because I'm working on a gitstatus prompt which depending on context can show REMOTE and/or PUSH_REMOTE information. For now I'm restricting it to "can show @{u}'s remote and branch name, and @{push}'s remote but not branch name." The @{u} branch name shows if different from the local; I'd like to show the @{push} branch name if different from the local. Will anyone ever make use of it? Dunno…

@romkatv
Copy link
Owner

romkatv commented Jan 6, 2022

Thanks for the details. Since there is no use case, I'm not included to add this field.

@romkatv
Copy link
Owner

romkatv commented Jan 11, 2022

Closing because I don't intend to do anything here.

@olets
Copy link
Author

olets commented Jan 11, 2022

👍

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

2 participants