Git-blame-someone-else
github.com
Git-blame-someone-else
1–10 of 100 posts
Re: Git-blame-someone-else
#2The commit hash of the blamed commit and all ones after that change, so the system works. One day we may be able to reliably/easily generate SHA-1 collisions to really get someone else to take the blame :-)
Re: Git-blame-someone-else
#3 git commit --amend --author=[...]Re: Git-blame-someone-else
#4`git replace` does it without rebasing, which is cleaner and likely to be left unnoticed by peers.
Re: Git-blame-someone-else
#5I'm going to use this as an example of why commit signing is really awesome for git repos.
Re: Git-blame-someone-else
#6I was expecting this to be like `git blame`, but to automatically check previous revisions for any lines touched by the current user. That would be a fun toy :-)
Re: Git-blame-someone-else
#7I runned a code formatter in our code base. Years later I was still 'blamed' for many things in our code as few files were untouched.
Re: Git-blame-someone-else
#8This somehow reminds me of how svn blame/praise was the same command.
Re: Git-blame-someone-else
#9The commit hash of the blamed commit and all ones after that change, so the system works. One day we may be able to reliably/easily generate SHA-1 collisions to really get someone else to take the blame :-)
Missed opportunity: append random whitespace characters to all subsequent commits so that the first N characters of commit id are retained.
Re: Git-blame-someone-else
#10if you're not already enforcing signed commits, you deserve it