git-extras
A collection of extra Git subcommands for common chores, such as summarizing a repository, deleting merged branches, and undoing commits.
Not checked by a trusted editor yet Last edited Outdated?
tj/git-extras
- Stars
- 18.1k
- Forks
- 1.2k
- Language
- Shell
- Licence
- MIT
- Last push
- 8 Oct 2026
On GitHub: GIT utilities -- repo summary, repl, changelog population, author commit percentages and more
Open on GitHubgit-extras adds dozens of new git subcommands, each a small script. Once installed they work like built-in commands, for example git summary for an overview of a repository’s commits and authors, or git delete-merged-branches to clean up finished work.
The project’s Commands.md file documents every command with examples, and the installation guide covers package managers on macOS, Linux, and Windows. Read a command’s description before using it, since several of them delete or rewrite things.
Even if you do not install it, the scripts are short and readable, which makes the repository a good place to learn how to build your own Git helpers.
Did this work for you?
No votes yet. Be the first.
If it did not work, the report form below tells the editors what went wrong.
See also
- 0033 The everyday Git workflow: status, add, commit, push, pull Git moves your changes through three places: the working folder, the staging area, and the commit history. These five commands, plus .gitignore… Beginner · Explains an idea · Any system Article Housekeeping · Setup 15 Oct 2026
- 0043 Delete local branches that are already merged A bash script that lists local branches fully merged into main and, if you ask, deletes them. It never touches the current… Intermediate · Step by step · Linux, macOS, Windows Script Housekeeping 15 Oct 2026
- 0044 A starter set of Git aliases Short names for the Git commands you type all day, such as a one-line status, a graph log, and a safe force… Beginner · Cheat sheet · Linux, macOS, Windows Script Git tools 15 Oct 2026
- 0357 Keep secrets out of git: .env files, gitignore and what to do after a leak Load passwords and API keys from an untracked .env file, commit a safe .env.example instead, catch mistakes before they are pushed, and… Beginner · Step by step · Any system Article Housekeeping · Secrets & access 15 Oct 2026
History
Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.
- Commitpedia +654 chars