This is great, thanks Kamran. Only issue I'm facing here is that any rebased appear twice, whilst temporary WIP commits also show up though they no longer exist. Currently my git standup command shows this:
Is there a way to either:
- Only show commits that still exist, by checking to see if the commit hash is present in any of the
origin branches. Could maybe include a git fetch to make sure it's up to date (though may be an undesired side effect for some).
- If that's not possible, could it filter and only show the latest commit with the same commit message? So if you have
add .vim to .gitignore committed twice due to a commit --amend or rebase it'd be great to be able to pass a flag that hides the repeated ones.
Ideally #1 would work best, as it would hide WIP commits too and seems to solve the problem closer to the root of the issue, but #2 would be a decent 80% fix towards making this more usable with those of us who rebase.
This is great, thanks Kamran. Only issue I'm facing here is that any rebased appear twice, whilst temporary WIP commits also show up though they no longer exist. Currently my
git standupcommand shows this:Is there a way to either:
originbranches. Could maybe include agit fetchto make sure it's up to date (though may be an undesired side effect for some).add .vim to .gitignorecommitted twice due to acommit --amendorrebaseit'd be great to be able to pass a flag that hides the repeated ones.Ideally #1 would work best, as it would hide WIP commits too and seems to solve the problem closer to the root of the issue, but #2 would be a decent 80% fix towards making this more usable with those of us who rebase.