You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Couldn't --recent be interpreted as what hasn't been pushed yet?
I propose that we implement both --recent and --branch.
--recent should then count commits between @ and @{upstream}, and --branch as @djberg96 suggests above.
Or is it over kill?
The upstream branch should probably be configurable, especially to support
git-flow workflows where the desired branch to compare to would likely be
called develop or dev.
I see there's a
local-commits
andcount
option, but nothing that gives me the number of commits versus the default branch.This is what I use for that currently:
git rev-list --count HEAD ^main
What I would like to be able to do is
git count -r/--recent
as a shortcut to achieve that.If such a thing already exists and I've missed it, please let me know and close this.
The text was updated successfully, but these errors were encountered: