Use cases
Where a fast git status pays for itself.
gity does one thing — make Git fast on repositories where it has gotten slow. These are the three places that slowness hurts most, and how the same daemon fixes each.
Large monorepos
Millions of tracked files, a six-second `git status`, and a team that pays the tax on every command. gity brings status back to milliseconds.
342× faster cold status on a ~250k-file repo (illustrative)
Read the scenario →CI/CD pipelines
Ephemeral runners clone, check out, and run `git status` on every job. `gity daemon oneshot` warms a cache for a single run without leaving a daemon behind.
Oneshot mode — no persistent daemon on the runner
Read the scenario →IDE & editor integration
VS Code and IntelliJ poll `git status` several times a second for gutter decorations. gity answers those polls from a warm cache instead of walking the tree.
Serves 10 status calls/sec from cache
Read the scenario →Get gity
Try gity on your biggest repo.
One command to install, one to register, and your monorepo starts feeling like a tiny one. MIT-licensed and free to use.