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: Show remotes in status #49

Open
LordMike opened this issue Oct 26, 2018 · 6 comments
Open

Feature: Show remotes in status #49

LordMike opened this issue Oct 26, 2018 · 6 comments

Comments

@LordMike
Copy link

I'd like a way to know, if any of my repos are ahead or behind their corresponding remotes. If possible, I'd also like to know this for any other branches I may have.

I do not know the relevant git commands, apart from the fact that git status will tell me if I'm behind or ahead...

I usually run mu status and then read through the messages, but it's quite cumbersome..

@Dadeerh
Copy link

Dadeerh commented Nov 3, 2018

One suggestion is to pass "-sb" to mu status. This is a much more compact list.
It doesn't help you in showing multiple branches though, but it's something.

@Dadeerh
Copy link

Dadeerh commented Nov 3, 2018

The better git command could be something along the lines of the second answer from here: https://stackoverflow.com/questions/7773939/show-git-ahead-and-behind-info-for-all-branches-including-remotes

I have a working version of mu-repo with a command added to do this atm..

@LordMike
Copy link
Author

LordMike commented Nov 5, 2018

Ooh, sb is a good one. But yea, something like the for-each ref would be great.

@rkhwaja
Copy link

rkhwaja commented Mar 22, 2019

You can make a git alias called bst which runs that, then you can run mu bst and get that output

@fabioz
Copy link
Owner

fabioz commented May 13, 2022

Closing since there are no plans to implement this -- pull requests welcome ;)

@fabioz fabioz closed this as completed May 13, 2022
@fabioz fabioz reopened this May 13, 2022
@fabioz
Copy link
Owner

fabioz commented May 13, 2022

Actually, this one has a pull request for it: #51

Still, the question there remains: why not just use a git alias?

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

4 participants