Discofork
Repository brief

jesseduffield/lazygit

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:44:34.513Z
3mo ago

jesseduffield/lazygit

jesseduffield/lazygit is an active, widely adopted Go repository for a simple terminal UI for git commands. It has a large user and contributor base, strong recent commit activity, and substantial fork interest, so forks are likely to be interesting if they add workflow, UI, or git-command enhancements rather than basic maintenance.

GitHub
Loading tags...
Stars75,259
Forks2,655
Default branchmaster
Last pushed2026-03-30T08:44:55Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose upstream unless you explicitly need this fork's pinned historical state. For normal adoption, the fork offers no visible functional advantage and appears to lag upstream by a large margin.

Choose this fork only if you specifically want its older custom workflow behavior and are prepared to maintain a deeply outdated codebase. For most users, upstream is the safer choice because this fork is stale and substantially behind.

Prefer upstream unless you specifically need this exact older snapshot; this fork adds no visible functionality and is substantially behind current upstream.

Choose this fork if you want a customized LazyGit with a few practical workflow enhancements and are willing to absorb merge debt. Choose upstream if you want the most current fixes and the lowest maintenance risk.

Adopters should prefer upstream unless they need this exact frozen state. This fork shows no added capability, while clearly lagging behind active upstream maintenance.

Choose this fork only if its custom-command and PTY/output changes are the point. For most adopters wanting a current, low-risk LazyGit, upstream is the better default because this fork is materially behind and more expensive to maintain.

Choose this fork only if its config-path, validation, or compatibility changes are specifically valuable to you. If you mainly want an up-to-date LazyGit, upstream is the safer default.

Choose this fork only if its custom Git workflow changes are specifically valuable to you. If you want current lazygit behavior, active maintenance, and upstream bug fixes, upstream is the safer choice.

Prefer upstream unless you specifically need this fork’s custom docs/branding and are prepared to carry a large maintenance burden. For most adopters, the staleness outweighs the limited fork-specific changes.

Prefer this fork only if you specifically need its local commit-flow customization or legacy compatibility behavior. For most users, upstream lazygit is the better choice because this fork is materially behind and likely missing many recent fixes and usability improvements.