4 ms·
I alias the command `git log origin/master.. --oneline`. (You could also do `git log @{upstream}.. --oneline` if you're diligent about configuring upstream bran
by oconnor663 8y ago
I alias the command `git log origin/master.. --oneline`. (You could also do `git log @{upstream}.. --oneline` if you're diligent about configuring upstream branches.) That shows you how many commits you have locally that you haven't pushed yet. I use them compulsively, almost as frequently as I use `git status`.
- JoshTriplett 8y agoWhat do you alias it to? (Also, I tend to use just `git log origin..` rather than spelling out `origin/master`.)
- oconnor663 8y agoPersonally "gout", which I now realize is a disease :p
- jwilk 8y agoFor me it's "git outgoing".
- jwilk 8y ago> I tend to use just `git log origin..` rather than spelling out `origin/master` Doesn't work for me: $ git log origin.. fatal: ambiguous argument 'origin..': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' $ git log origin.. -- fatal: bad revision 'origin..'
- oconnor663 8y agoMaybe it will work if you do `git branch --set-upstream-to=origin/master` first? But yeah, this config issue is why I don't use @{upstream} much.
- jolmg 8y agoEven shorter: `git log @{u}..`
- glandium 8y agoI find `git show-branch --topics origin/master` (optionally adding branches) to be more useful.