> You can invoke git-who as git who by setting up an alias in your global Git config
This works even without the alias, by the way: by default `git whatever` will search your path for `git-whatever` and execute it.
Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
11–20 of 130 posts
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#12By the way, git blaming is really misunderstood by a lot of people; its NOT about who did it, its about which commit is to blame -- that's different.
Ideally, you find the context for why a change was made
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#13Cool stuff. I like using Git via the CLI, but when it comes to blame, I simply use the preview UI of the VSCode GitLens extension. It takes half a second to launch it from the command palette and inspect the blame.
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#14By the way, git blaming is really misunderstood by a lot of people; its NOT about who did it, its about which commit is to blame -- that's different.
Isn't this sort of an inconsequential point? The commit still has one and only one author and that's almost certainly what I'm looking for so I know who to go ask questions about their code. I also use it to find the commit but less frequently.
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#15I 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.
git help mailmapRe: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#16By the way, git blaming is really misunderstood by a lot of people; its NOT about who did it, its about which commit is to blame -- that's different.
Isn't this sort of an inconsequential point? The commit still has one and only one author and that's almost certainly what I'm looking for so I know who to go ask questions about their code. I also use it to find the commit but less frequently.
I mean, no. If you work on a codebase that's been going for more than a few years, the author likely doesn't even work there anymore. The commit is the important thing.
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#17By the way, git blaming is really misunderstood by a lot of people; its NOT about who did it, its about which commit is to blame -- that's different.
Isn't that what git bisect is for?
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#18By the way, git blaming is really misunderstood by a lot of people; its NOT about who did it, its about which commit is to blame -- that's different.
Isn't this sort of an inconsequential point? The commit still has one and only one author and that's almost certainly what I'm looking for so I know who to go ask questions about their code. I also use it to find the commit but less frequently.
On a small team I usually already know who wrote the code I'm reading, but it's nice to see if a block of code is all from the same point in time, or if some of the lines are the result of later bugfixing. It's also useful to find the associated pull request for a block of code, to see what issues were considered in code review, to know whether something that seems odd was discussed or glossed over when the code was merged in the first place.
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#19By the way, git blaming is really misunderstood by a lot of people; its NOT about who did it, its about which commit is to blame -- that's different.
I have seen `git blame` used to blame specific people. I've seen it work. Some of those people deserved some blame.
The manpage explains what the command does. How and why it's used is up to the user.
Re: Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming
#20Earlier quoted context omitted.
Isn't this sort of an inconsequential point? The commit still has one and only one author and that's almost certainly what I'm looking for so I know who to go ask questions about their code. I also use it to find the commit but less frequently.
On a small team I usually already know who wrote the code I'm reading, but it's nice to see if a block of code is all from the same point in time, or if some of the lines are the result of later bugfixing. It's also useful to find the associated pull request for a block of code, to see what issues were considered in code review, to know whether something that seems odd was discussed or glossed over when the code was…
I find the GitHub blame view indispensable for this kind of code archeology, as they also give you an easy way to traverse the history of lines of code. In blame, you can go back to the previous revision that changed the line and see the blame for that, and on and on.
I really want to find or build a tool that can automatically traverse history this way, like git-evolve-log.