HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sinclairtarget
git-who
Go2025–2025
sinclairtarget / git-who

git-who

Git blame for file trees

2Distinct people
2Mentions
0Explicit recommenders
2.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Git blame for file trees

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2025-03-18 20:20:09 UTC to 2025-03-19 18:42:00 UTC.

012025-03-18 20:00:00 UTC to 2025-03-18 21:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 18, 20:002025-03-18 21:00:00 UTC to 2025-03-18 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-18 22:00:00 UTC to 2025-03-18 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-18 23:00:00 UTC to 2025-03-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 00:00:00 UTC to 2025-03-19 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 01:00:00 UTC to 2025-03-19 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 02:00:00 UTC to 2025-03-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 03:00:00 UTC to 2025-03-19 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 04:00:00 UTC to 2025-03-19 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 05:00:00 UTC to 2025-03-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 06:00:00 UTC to 2025-03-19 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 07:00:00 UTC to 2025-03-19 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 19, 07:002025-03-19 08:00:00 UTC to 2025-03-19 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 09:00:00 UTC to 2025-03-19 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 10:00:00 UTC to 2025-03-19 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 11:00:00 UTC to 2025-03-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 12:00:00 UTC to 2025-03-19 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 13:00:00 UTC to 2025-03-19 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 14:00:00 UTC to 2025-03-19 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 15:00:00 UTC to 2025-03-19 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 16:00:00 UTC to 2025-03-19 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 17:00:00 UTC to 2025-03-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-19 18:00:00 UTC to 2025-03-19 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 19, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 18, 20:002025-03-18 20:00:00 UTC2025-03-18 21:00:00 UTC110
Mar 18, 21:002025-03-18 21:00:00 UTC2025-03-18 22:00:00 UTC000
Mar 18, 22:002025-03-18 22:00:00 UTC2025-03-18 23:00:00 UTC000
Mar 18, 23:002025-03-18 23:00:00 UTC2025-03-19 00:00:00 UTC000
Mar 19, 00:002025-03-19 00:00:00 UTC2025-03-19 01:00:00 UTC000
Mar 19, 01:002025-03-19 01:00:00 UTC2025-03-19 02:00:00 UTC000
Mar 19, 02:002025-03-19 02:00:00 UTC2025-03-19 03:00:00 UTC000
Mar 19, 03:002025-03-19 03:00:00 UTC2025-03-19 04:00:00 UTC000
Mar 19, 04:002025-03-19 04:00:00 UTC2025-03-19 05:00:00 UTC000
Mar 19, 05:002025-03-19 05:00:00 UTC2025-03-19 06:00:00 UTC000
Mar 19, 06:002025-03-19 06:00:00 UTC2025-03-19 07:00:00 UTC000
Mar 19, 07:002025-03-19 07:00:00 UTC2025-03-19 08:00:00 UTC000
Mar 19, 08:002025-03-19 08:00:00 UTC2025-03-19 09:00:00 UTC000
Mar 19, 09:002025-03-19 09:00:00 UTC2025-03-19 10:00:00 UTC000
Mar 19, 10:002025-03-19 10:00:00 UTC2025-03-19 11:00:00 UTC000
Mar 19, 11:002025-03-19 11:00:00 UTC2025-03-19 12:00:00 UTC000
Mar 19, 12:002025-03-19 12:00:00 UTC2025-03-19 13:00:00 UTC000
Mar 19, 13:002025-03-19 13:00:00 UTC2025-03-19 14:00:00 UTC000
Mar 19, 14:002025-03-19 14:00:00 UTC2025-03-19 15:00:00 UTC000
Mar 19, 15:002025-03-19 15:00:00 UTC2025-03-19 16:00:00 UTC000
Mar 19, 16:002025-03-19 16:00:00 UTC2025-03-19 17:00:00 UTC000
Mar 19, 17:002025-03-19 17:00:00 UTC2025-03-19 18:00:00 UTC000
Mar 19, 18:002025-03-19 18:00:00 UTC2025-03-19 19:00:00 UTC101

What Hacker News says

2 sources
weebst·Mar 18, 2025Submission

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

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!
252 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.