Guide · Open source
How to use git-blame-someone-else: install and change a commit author
Updated · written with AI from the project's own documentation and checked against our catalogue data
git-blame-someone-else is a small shell script that changes the author and committer recorded on a git commit to a name you choose. This guide shows how to clone, install and run it, and explains the warnings the author gives. It is written for readers who want to understand how git stores authorship, not for use on real projects.
git-blame-someone-elsejayphelps/git-blame-someone-else · ★ 11.7k · MIT Install options & downloads Quick start
- 1Clone the repository. Run git clone with the repository URL from the README to download the project into a local folder.
- 2Enter the project folder. Change into the git-blame-someone-else folder with cd.
- 3Install system-wide. Run sudo make install. This needs sudo access and make on your system.
- 4Create a throwaway test repository. Make a separate repository with a few test commits so that any changes cannot affect real work.
- 5Run the command. Run git blame-someone-else with an author name and a commit reference, as shown in the README.
- 6Check the result. Inspect the commit with git to confirm the author and committer fields changed as expected.
What git-blame-someone-else does
The script rewrites the author and committer information attached to a git commit. The README says it changes both fields, not only the author.
The author wrote it as a joke to show that the author field can be changed. The README's own example is a fake commit attributed to Linus Torvalds, which the README says he did not approve.
What you need before installing
The project's prerequisites are git, make, and sudo access for the install step. The install uses sudo make install, so it copies files system-wide and needs administrator rights.
Clone the repository and install it on a machine where you can test safely, such as a throwaway test repository.
- git
- make
- sudo access for the install step
Install git-blame-someone-else
Clone the repository, move into the project folder, then run the install step. The README lists these three commands in order.
$ git clone https://github.com/jayphelps/git-blame-someone-else.git
$ cd git-blame-someone-else
$ sudo make installRun the blame-someone-else command
The README gives one usage pattern: pass an author name and a commit reference. Use it only in a disposable test repository, because the README warns that it can alter or delete history.
- <author> is the name you want recorded as the author.
- <commit> is the commit you want to change.
$ git blame-someone-else <author> <commit>Warnings to read before you run it
The README says the script can damage a repository if misused. It says the script is a joke and asks users not to run it against a production repository.
Because it changes commit metadata, it falsifies who wrote the code. Do not use it where you need an accurate record of authorship.
- Do not run it on shared or production repositories.
- Do not use it to keep an audit trail.
- If you are not comfortable undoing git history changes, do not use it.
Alternatives for real history work
The source names git filter-repo and git rebase as comparable projects. Both are general tools for changing git history, so they are a better starting point if you need to edit commits for a real project.
This page does not describe how to use those tools. Read their own documentation before using them.
What people use it for
- Seeing for yourself that git stores author and committer as fields that can be set
- Demonstrating to a class or team how commit metadata works, using a disposable repository
- Trying a small, humorous shell script to learn how a git command extension is structured
Frequently asked questions
Is git-blame-someone-else free to use?
The project is released under the MIT licence, according to the source. Read the licence file in the repository for the full terms.
What do I need to install git-blame-someone-else?
The source lists git, make, and sudo access for the install step. The install is done by cloning the repository and running sudo make install.
Is git-blame-someone-else safe to use on my project?
The README says no for production or shared repositories. It warns the script can alter or delete history if misused, so test it only in a throwaway repository.
Why would I use git-blame-someone-else?
The source says it is mainly useful to see how git stores authorship. It is not presented as a tool for real work.
What are alternatives to git-blame-someone-else?
The source names git filter-repo and git rebase as comparable projects. Both can change git history and are better suited to real repository work.
Does it change only the author?
No. The README says it changes the listed committer as well as the author of the commit.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use git-blame-someone-else only in a throwaway test repository if you want to see how git stores author and committer data. Teams with shared repositories, anyone who needs an accurate audit trail, and beginners should choose a proper history tool such as git filter-repo or git rebase instead.
Install options & downloads