Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming

github.com

Post reply on HN
Print view View original

1–10 of 130 posts

Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming

#1

Post by weebst »

I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this.

It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options.

If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!

Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
github.com

Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming

#3

Post by jtwaleson »

andrewfromx wrote: post #2

I like it. A problem I had right away is some people commit using two different emails. Like one from home computer and one from work computer. Would be nice to be able to define them as the same thing.

That's what the mailmap is for.

Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming

#4

Post by sebastianlay »

andrewfromx wrote: post #2

I like it. A problem I had right away is some people commit using two different emails. Like one from home computer and one from work computer. Would be nice to be able to define them as the same thing.

You might be able to do that with built-in git functionality called gitmailmap. It is basically a file where you can map multiple names and emails to the same one.

Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming

#5

Post by jtwaleson »

Very cool, I'm working on something similar as part of a bigger project (not TUI related). I'm interested in how you did blame caching, will take a look at the implementation. I am trying to do a "forward blame" so that the blame of new commits can be created very quickly. Happy to exchange some thoughts around this!
Post reply on HN