A git client that leaves you alone.
Most git clients are good at git. The trouble is what comes with them: a price, a sign-in, a cloud, an assistant. Git Revenge is the client without the rest.
It’s free. All of it.
There’s no paid tier, no trial that runs out, and no licence to buy before you can open a private repository or use it at work. Every feature is in the one download. The source is on GitHub under Apache-2.0, so it stays that way.
Your code is nobody else’s business.
You never make an account or sign in. There’s no telemetry, no cloud sync, and no AI reading your diffs. The app makes one request on its own: at startup it asks GitHub whether a newer release exists. Settings turns that off.
It stays quick when the repository is huge.
The graph reads history just ahead of where you’re looking instead of all of it. On the Linux kernel, with 1.5 million commits, the first screen arrives in under half a second and scrolling stays smooth all the way down.
It’s your git, not a copy of it.
Git Revenge drives the
gityou already installed, so your config, hooks, aliases, signing keys, credential helpers and SSH agent all work as they do in a terminal. Commit in a terminal and the app shows it within a second. Stop using the app tomorrow and nothing about your repositories has changed.It tells you first, and lets you take it back.
A merge or rebase says which files will conflict before it runs. Commits, merges, rebases, resets and pulls can be undone with one key. Anything that throws work away asks, and says what you’d lose.
It’s small.
The download is under 20 MB, because the app uses the web view your system already has instead of shipping a browser of its own. Everything it remembers is one settings file and your own git config.
| What you may be used to | Git Revenge |
|---|---|
| A subscription for private repositories, or for the “pro” features | Free, for everything |
| An account before you can open a repository | No account, ever |
| Usage analytics, on unless you find the switch | No telemetry to switch off |
| A bundled git with settings of its own | The git you already use |
| A long wait on a big monorepo | A first screen in under a second |
| An assistant that sends your code somewhere | No AI |
The hard parts of git, made visible.
Each of these is a walkthrough you can follow in a practice repository, without touching real work.
Commit part of a file
Stage a hunk or a few lines, write a message, Ctrl+Enter.
Tidy a branch
Drop, squash and fold in fixups, and see the result before you run it.
Resolve a conflict
Pick a side for each place, or type the answer. No conflict markers.
Undo a mistake
Merged the wrong branch? Ctrl+Z puts it back.
Find a commit
Search by message, author, SHA or trailer, through the whole history.
Find what broke it
Answer Good or Bad as it halves the range, down to the one commit.
All of git, none of the waiting.
Built for the repositories other clients give up on, and comfortable on small ones too.
A graph you can read
Commits in date order with your main branch as a spine, a line for each day, bot and docs commits folded away, and a ruler at the edge that shows where the branches, tags and search matches are.
Everyday git
Stage files, hunks or single lines. Commit, amend, stash, branch, tag, merge, rebase, cherry-pick, reset and revert. Signed commits if your config signs them.
The hard parts
An interactive rebase editor that shows the branch as it will be. A conflict tool built around the result. Bisect, blame, file history, the reflog and git notes.
Branch care
Branches have kinds, so release and bot branches stop crowding your work. Merged branches clean themselves up after a pull, squash merges included, and stacked branches restack in one click.
Previews, not only diffs
Markdown, images, CSV, JSON, YAML, TOML, LaTeX, Mermaid and PDF files can be shown rendered, beside the usual unified or split diff.
Many repositories
Repositories open in tabs that come back when you restart. Put related ones in a group and fetch or pull them all from one dashboard. Worktrees are listed and open as tabs.
Editors for git’s own files
See every ignore rule that applies and which one decides a path. Edit git config with a line on what each setting does, where a value comes from, and a backup on every save.
Insights for sprint reviews
What shipped in a window, which branches are stuck or would conflict, and where the hotspots are. It’s worked out from the repository alone, so anyone gets the same numbers.
Keyboard first, when you want
A command palette holds every command. Common ones have shortcuts you can change, and menus, lists and dialogs all work without a mouse.
What it doesn’t do
Git Revenge knows git, and nothing about the site your repository is hosted on. It won’t open pull requests, show review comments or move a ticket. Smart links turn a ticket key in a commit message into a link, and that link opens in your browser.
It also needs git 2.40 or newer on your machine, because it doesn’t bring its own. If you want pull requests inside your git client, or an assistant to write commit messages, another client will suit you better.
Get it
macOS
With Homebrew, or the signed and notarized disk image.
brew install --cask git-revenge/tap/gitrevenge
Windows
With winget, which keeps it up to date, or the signed installer from the latest release.
winget install GitRevenge.GitRevenge
Linux
From the signed apt and dnf repositories, for Ubuntu, Debian and RHEL 9 and 10. Add one once; the install guide has the commands.
sudo apt install gitrevenge sudo dnf install gitrevenge
Documentation
Git Revenge is an independent project, and it’s free to use. If it saves you time, you can sponsor it. Bugs and ideas go to the issue tracker.