Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderThis has saved me so many times. I’m sure I would have lost my job a while ago had I not been able to use this, it’s one of my most actively use tools. I’m sure eventually I’ll be losing my job, but at least this repo has enabled me to keep it a little bit longer.
What is more, you can: 1. clone https://github.com/torvalds/linux into https://github.com/<YOURNAME>/linux. 2. push a fake "torvalds" commit into your repo. 3. check the SHA of the the commit that you made. 4. the commit will be visible at the original repo URL with your SHA (https://github.com/torvalds/linux/commit/<SHA>), with no indication whatsoever that this is coming from a different repo I have reported this problem to GitHub a while ago and they replied to me that this is a well known feature of…
"Show HN" is for projects you personally have created. It's not legit to post someone else's project as if it were your own. We take submission privileges away from accounts that do this. The Show HN rules are here: https://news.ycombinator.com/showhn.html. Comments moved to https://news.ycombinator.com/item?id=11049993, which was posted earlier anyway.
Should probably use this moment to plug my (opposite) project, git-upstage, which lets you claim credit for someone else's work and backdate it so it looks like you did it first: https://github.com/SilasX/git-upstage
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 3
- Total points
- 823
- Total comments
- 242
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2016-02-06 | Git-blame-someone-else – Blame someone else for your bad codeFirst breakout | mablae | 149 | 65 |
| 2016-02-07 | Git-blame-someone-else – Blame someone else for your bad code | swapagarwal | 166 | 3 |
| 2019-09-03 | Git Blame-Someone-Else | dcminter | 1 | 0 |
| 2019-09-18 | Git Blame-Someone-Else | dcminter | 225 | 66 |
| 2021-07-26 | Git-blame-someone-elseBest thread | swyx | 230 | 96 |
| 2023-06-03 | Git Blame-Someone-ElseLatest 20+ point return | MrGagi | 52 | 12 |