PHphysicsguy·Mar 19, 2025
I like this one the best:
https://github.com/jayphelps/git-blame-someone-else
In Show HN: "Git who" – A new CLI tool for industrial-scale Git blamingjayphelps
git-blame-someone-else
Shell2016–2025
jayphelps / git-blame-someone-else
git-blame-someone-else
Blame someone else for your bad code.
16Distinct people
18Mentions
0Explicit recommenders
11.7KGitHub stars
What to know before exploring
What it is
Blame someone else for your bad code.
GitHub
Where it is used
No documented product use was verified in the last source check.
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, 3:56:07 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 year18 dated mentions
Observed mentions: 2016-02-06 21:31:04 UTC to 2025-03-19 06:40:51 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
18 sourceshttps://github.com/jayphelps/git-blame-someone-else is a pretty good reason to sign your commits
In I don’t think you should sign your Git commitsThank god for https://github.com/jayphelps/git-blame-someone-else
In FTX "insurance fund" calculated by multiplying trading volume by random numberBut funny enough is that there is a commit where it pretends to be Linus https://github.com/jayphelps/git-blame-someone-else/commit/e...
In Git Blame-Someone-ElseFinally a valid use case for git-blame-someone-else
https://github.com/jayphelps/git-blame-someone-else
In Improved workflow and new role for pricing changes>If GitHub required email address verification, how would this be done?
author data in a commit can be replaced by repository owners. You can replace all old email addresses to new ones https://github.com/jayphelps/git-blame-someone-else https://github.com/SilasX/git-upstage
In How to take credit for someone else's work on GitHubNow you're thinking like the author of git-blame-someone-else: https://github.com/jayphelps/git-blame-someone-else
In How to take credit for someone else's work on GitHubIt’s not just blame. GitHub uses commits to build the contributor list on your repo home page, so you can make it look like it has some famous contributors:
https://github.com/jayphelps/git-blame-someone-else/graphs/c...
In Git-blame-someone-elseWhich is almost exactly how this works:
https://github.com/jayphelps/git-blame-someone-else/blob/8d8...
In Git-blame-someone-elseShowing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.