3 ms·
Neat. I may end up using this. fwiw as feedback: - 1 would be far more useful to me if it suggested reviewers based on the files changed in this commit / bra
by Groxx 10y ago
Neat. I may end up using this.
fwiw as feedback:
- 1 would be far more useful to me if it suggested reviewers based on the files changed in this commit / branch / ?. probably true for most large projects.
- 7 is a thing I made myself as well (though yours is noticeably faster), and I LOVE it. glad to see it appearing elsewhere :)
- what Zikes said. non-interactive input is a must for script-ability (e.g. to add an alias to output one option).
- easily readable awk and bash... nice work. scripts like this are really handy for teaching people about sane complex bash scripting. I'll spread it around at work a bit :)
- netcraft 10y agoagreed re: #7, heres another project I use that just does that: https://github.com/paulirish/git-recent https://github.com/paulirish/git-recent
- Goopplesoft 10y agoI have the following aliased to gbl: git for-each-ref --sort=-committerdate refs/heads/ With formatting: git for-each-ref --sort=-committerdate refs/heads/ --format='%(HEAD) %(color:yellow)%(refname:short)%(color:reset) - %(color:red)%(objectname:short)%(color:reset) - %(contents:subject) - %(color:cyan)%(authorname)%(color:reset) (%(color:green)%(committerdate:relative)%(color:reset))'