What does HackerNews think of git-blame-someone-else?

Blame someone else for your bad code.

Language: Shell

FTX "insurance fund" calculated by multiplying trading volume by random number | Oct 2023
Expand Context ↕
Thank god for https://github.com/jayphelps/git-blame-someone-else
Signing Git Commits with Your SSH Key | Sep 2022
Expand Context ↕
https://github.com/jayphelps/git-blame-someone-else
Netlify: Improved workflow and new role for pricing changes | Jun 2022
Expand Context ↕
Finally a valid use case for git-blame-someone-else

https://github.com/jayphelps/git-blame-someone-else
How to take credit for someone else's work on GitHub | Mar 2022
Expand Context ↕
>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
How to take credit for someone else's work on GitHub | Feb 2022
Expand Context ↕
Now you're thinking like the author of git-blame-someone-else: https://github.com/jayphelps/git-blame-someone-else
Who wrote this shit? | Jan 2022
Expand Context ↕
https://github.com/jayphelps/git-blame-someone-else