"Git who"

Dev tools

git cli

SHOW HN2025

252points
127comments
#236of 3,837 in 2025
Top 7%of 2025 by points

How HN took it

MixedNo clear lean

15 positive, 17 neutral or asking, 0 mixed, 3 critical, out of 35 comments about the project. Thread score +0.34.

Idea: 3 for, 2 againstExecution: 4 for, 0 againstDocs: 1 for, 1 againstPerformance: 2 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Fast on large repositories

    From 1 comment
    • This is fantastic! I love it. Pretty quick too... For a rails codebase that is ~18 years old, has 1695 committers and more than 220,000 commits: ``` time git who ... real…
      dcchambers on HN
  • Useful, nice CLI tool

    From 3 comments
    • Lovely tool. Thanks for the release! I had some fun with it before calling it a day. Here is my personal wishlist after a short test-drive. - Blame-based stats. While it is nice…
      m000 on HN
    • I love TUI tools but I'm not too familiar with Golang, now I am thinking I should start looking into using go for TUIs this is a great tool!
      numbers on HN
    • I love CLI tools, plus it is open source!
      eddiejaoude on HN

Objections

  • Blame is about the commit, not the author

    From 2 comments
    • By 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.
      lionkor on HN
    • I don't think the comparison to git blame is needed/warranted. While the 'blame' in git blame suggests the tool is about identifying authors its main purpose is to identify…
      account42 on HN
  • Build requires Ruby and rake, not just Go

    From 1 comment
    • Followed the link, and the README said: > This requires that you have Go, Ruby, and the rake Ruby gem installed. That doesn't cut it for me. git - once built - depends on C…
      einpoklum on HN
  • Attribution can mislead, e.g. squashed or reformatted commits

    From 1 comment
    • One thing to note, maybe particularly with reference to the “who wrote vim” analysis⁰, is that depending on workflow this can attribute more to internal contributors than you…
      dspillett on HN

Requests

  • Pattern-based file inclusion and exclusion

    From 2 comments
    • Lovely tool. Thanks for the release! I had some fun with it before calling it a day. Here is my personal wishlist after a short test-drive. - Blame-based stats. While it is nice…
      m000 on HN
    • This is great. I do this sort of git-blame accounting to track how much code is written by AI versus humans in each release of my app. My "blame script" has been slowing down as…
      anotherpaulg on HN
  • Blame-based ownership stats for trees

    From 1 comment
    • Lovely tool. Thanks for the release! I had some fun with it before calling it a day. Here is my personal wishlist after a short test-drive. - Blame-based stats. While it is nice…
      m000 on HN
  • Configuration file support

    From 1 comment
    • Lovely tool. Thanks for the release! I had some fun with it before calling it a day. Here is my personal wishlist after a short test-drive. - Blame-based stats. While it is nice…
      m000 on HN
  • Homebrew release

    From 1 comment

Questions

  • How to show more than the top ten rows

    From 1 comment
    • Cool, but how do I increase the number of rows? Is it always just the top ten?
      natemwilson on HN
  • Why Ruby is needed when the code is mostly Go

    From 1 comment
    • This looks like an almost pure Golang program, but still has a Ruby dependency. Is there a component/library that Ruby provides, that Go doesn't have? Or some other logic going on?
      unquietwiki on HN

Alternatives named

  • git shortlog

    From 2 comments
    • For a low-tech version of this, I have long had an alias (which I call "nerdwars") to "git shortlog -ns --no-merges" which just gives the number of commits by contributor from…
      seanhunter on HN
    • I don't think the comparison to git blame is needed/warranted. While the 'blame' in git blame suggests the tool is about identifying authors its main purpose is to identify…
      account42 on HN
  • git-blameall

    From 1 comment
    • I've been carrying around a copy of "git blameall" for years - looks like https://github.com/gnddev/git-blameall is the same one - that basically does this, but keeps it all…
      eichin on HN
  • git-praise

    From 1 comment
    • Alternatively git praise https://github.com/ansman/git-praise
      lelandfe on HN
  • tj/git-extras git summary

    From 1 comment
    • I've been using `git summary` from tj/git-extras for a while. It seems to do a similar job.
      syhol on HN
  • MergeStat

    From 1 comment
    • This is such a cool tool. It's a better approach to solving many of the questions I built MergeStat to answer (https://github.com/mergestat/mergestat-lite). It's been some time,…
      patrickdevivo on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/43404548)