Skip to main content
← back to field notes
4 min readDevelopment

A git client your security team has nothing to ask about

gitsecuritytoolsdeveloper-experienceopen-source

Most companies standardize on git and a host, then let you pick your own client. That's great until security sends out a memo about tools that upload code to AI services, and you realize you have no idea what yours does. You picked it, so you get to answer for it.

Git Revenge is an easy one to answer for. It also won't do everything you'd want at work, and I'll cover that part too.

What it sends off your laptop​

This is the complete list:

WhatWhere it goesWhen
An update checkGitHub's releases API, for the latest version numberAt startup. Settings turns it off
Fetch, pull, push, cloneYour remotes, through your own git and credentialsWhen you click one
A linkYour web browserWhen you click a ticket or URL link

There are no accounts, crash reports or usage stats. Rendered previews don't fetch anything, so an image link in a README shows up as a link and doesn't load. Insights are computed from the repo itself, without calling your host's API.

That table comes straight from the install guide. The code is Apache-2.0 on GitHub, so nobody has to take my word for any of it.

AI isn't switched off behind a setting. There isn't any. The project plan lists AI as a non-goal, along with accounts and cloud sync.

Your company's git setup keeps working​

Company repos come with things a client can quietly break: commit hooks, a proxy, single sign-on to the host, signing rules. Clients that bundle their own git library sometimes skip hooks or ignore your credential helper. You find out when a commit that should have failed the lint hook lands on main.

Git Revenge runs the git installed on your machine for everything, so:

  • Pre-commit, commit-msg and pre-push hooks run the way they do in a terminal.
  • If Git Credential Manager handles SSO to your host, the app goes through it. When git needs a password or passphrase, the app asks in a dialog and doesn't store it.
  • Proxy and certificate settings come from your git config. If git fetch works in a terminal, it works here.
  • If commit.gpgsign is set, commits made in the app are signed with GPG or SSH. Signed commits get a verification badge.

Branch protection makes sense in it, too. When a push is refused because main only takes changes through a pull request, the error says exactly that, in one line, and offers Push to a new branch….

The parts I use at work​

Set your Jira or Azure Boards pattern once, and PAY-1432 in a commit message or branch name becomes a link to the ticket. The app builds the URL and never calls the tracker, so there's no API token to look after.

Mark production and staging as Environment branches, and the app asks before anyone force pushes to them or deletes them.

Before a merge or rebase runs, you get a preview of which files will conflict and in how many places. It works that out without touching the working tree, so you can back out before anything gets messy.

After a pull, it can also delete local branches whose pull requests were squash-merged and deleted on the host. git branch --merged can't spot those, and they pile up fast. If it removes one you wanted, Undo brings it back.

And if your employer has one of those enormous repos, history loads as you scroll instead of all at once.

No purchase to approve​

It's free. You never activate a license key or count seats, and there's no renewal or expense report. Put it on the work laptop and the home machine. Apache-2.0 is the same license your legal team has already approved for half the dependencies in your build.

What it won't do at work​

Read this before you suggest it in the team channel.

It doesn't do pull requests. Reviews, comments and approvals stay on your host's website, and that's a stated non-goal. If your team does PR review inside the client, this isn't your tool.

There's no vendor behind it, just one maintainer, and that's me. I can't offer a support contract, an SLA or a SOC 2 report. If your company needs those before it approves software, Git Revenge won't get through procurement. That's a fair call for them to make.

A signed installer can still get stopped on a managed laptop. The Windows installer is signed, but SmartScreen might warn you anyway, and an application control policy may only allow publishers IT has already approved. Ask before you try to work around either one.

It's young, and releases come often. If something breaks on your company's setup, please open an issue with the error.

It doesn't scan for secrets either. Keep your company's pre-commit secret checks. The app runs them, but it doesn't add its own.

If you have to ask first​

If your company has an approval process for developer tools, this is what I'd send:

  • the privacy and network notes
  • the source code and its Apache-2.0 license
  • a line saying it uses the company's own git install, hooks and credential helpers, and keeps its settings in one local file
  • a line saying the Windows installer is signed, the macOS build is signed and notarized, and Linux installs come from a signed package repository

That should be a short conversation. A tool with an account, cloud sync and an AI toggle usually isn't.

It needs git 2.40 or newer, and your company's developer image almost certainly has it already. Installers are on the releases page.

field notes

you may also enjoy

more from this thread of thought

Three of me in one git log: keeping identities apart with includeIf
Nov 19, 2026

Three of me in one git log: keeping identities apart with includeIf

read more →
A free git client for private repos and self-hosted git
Nov 18, 2026

A free git client for private repos and self-hosted git

read more →
Your giant repo is slow because nobody tuned git
Nov 17, 2026

Your giant repo is slow because nobody tuned git

read more →
Introducing Git Revenge, and whether you should use it
Nov 5, 2026

Introducing Git Revenge, and whether you should use it

read more →
The cost of maintaining open source
Oct 27, 2026

The cost of maintaining open source

read more →
Is there a future without AI?
Oct 25, 2026

Is there a future without AI?

read more →
the field notes

recently written