Written by @iluxav from the project's code and releases, not by its maintainers. Last updated for v0.66.3 (2026-11-07), so it may lag behind newer releases.
Thanks. Marked useful.
Thanks. The report went to osfeed, and the line gets checked against the repository.
Stage single lines, rebase interactively, cherry-pick, bisect, resolve conflicts and undo mistakes in git with one key each, from a terminal window.
What you can do with lazygit
Squash, fixup, drop, reword and reorder commits with an interactive rebase driven by keys.
Wrong?
Add staged changes to an older commit, not just the last one.
Wrong?
Copy commits and paste them onto another branch.
Wrong?
Find the commit that introduced a bug with git bisect, marking commits good or bad.
Wrong?
Move or remove parts of a commit by building a custom patch from it.
Wrong?
Undo and redo git actions using the reflog.
Good to know
Covers actions recorded in the reflog; not working-tree changes.
Wrong?
Create, switch and remove git worktrees.
Wrong?
Show all 23
Show only the commits that touch a path, or by an author.
Wrong?
See the commit graph and compare any two commits.
Wrong?
Bind your own commands, with prompts and menus, to keys.
Wrong?
Show diffs through another renderer such as delta, difftastic or `git diff --color-words`.
Wrong?
Resolve all conflicts in chosen files as ours, theirs or both, or open the external merge tool.
Wrong?
Add a fork's remote by typing its owner, and check out a branch from it.
Wrong?
Open a pull request or commit page on the repository's hosting service from lazygit.
Wrong?
See a GitHub pull request's status next to its branch and open it with one key.
Good to know
GitHub only; needs the `gh` CLI logged in.
Wrong?
Start and finish git flow features, releases and hotfixes, with legacy git-flow or git-flow-next.
Good to know
Needs git-flow or git-flow-next installed.
Wrong?
Reorder, hide and regroup the side panels and their tabs.
Wrong?
Push or pull the branches of a stack together from its topmost branch.
Good to know
Push includes branches with upstreams; pull uses last-fetch data and skips other worktrees. Rewritten-upstream detection needs remote reflogs.
Wrong?
Use different colors for dark and light terminal backgrounds.
Good to know
Automatic detection falls back to dark when the terminal does not report its background; set `gui.colorScheme` explicitly if needed.
Wrong?
Navigate, copy and open selected diff lines directly from the main view.
Good to know
Interactive renderer output requires OSC 1717 support.
Wrong?
Push or delete multiple selected Git tags in one operation.
Good to know
Requires selecting tags in the tags view.
Wrong?
Inspect and discard nested repositories or directories left behind by removed submodules.
Good to know
Nested repositories and worktrees cannot be staged; add a repository as a submodule if it should be tracked. Worktrees must be removed individually.
Wrong?
Before you upgrade lazygit
Newest firstLazygit ignores submodules whose names or paths lead outside the repository, including paths through symlinks. Submodule deletion refuses Git directories outside the current worktree's modules directory.
Read the evidence
Wrong?
`.gitmodules` parsing recognizes section headers and keys only at the start of a line, so comments no longer create entries and `path=` inside a URL no longer overrides a submodule path.
Read the evidence
Wrong?
The narrow selection bar appears on both edges of the focused diff. Actions report an error when selected diff lines or their file cannot be resolved, instead of silently doing nothing.
Read the evidence
Wrong?
Show 22 older
Lazygit exits with an error message when the repository or worktree disappears.
Read the evidence
Wrong?
Double-click timing uses when clicks were read, so queued clicks remain recognizable. The terminal is restored more reliably after a panic.
Read the evidence
Wrong?
Use Go 1.26.0 or newer to build v0.66.2; `go.mod` previously required Go 1.25.0.
Read the evidence
Wrong?
Focus a diff with `0`; use `space` to stage or unstage, `a` for line selection, `v` for a range and `d` to discard. The separate staging panel is gone.
Read the evidence
Wrong?
Build custom patches directly in a commit's main diff; the separate patch-building panel is gone.
Read the evidence
Wrong?
Rename `gui.wrapLinesInStagingView` to `gui.wrapLinesInDiffView` and `gui.useHunkModeInStagingView` to `gui.useHunkModeInDiffView`. Writable configs migrate automatically; read-only configs must be updated before launch.
Read the evidence
Wrong?
Move `gui.authorColors` and `gui.branchColorPatterns` under `gui.theme`. Writable configs migrate automatically; update read-only configs before launch.
Read the evidence
Wrong?
Replace `gui.branchColors` with `gui.theme.branchColorPatterns`, converting each prefix to an escaped `^prefix(/|$)` regex. If patterns already override it, remove `gui.branchColors`. Writable configs migrate automatically.
Read the evidence
Wrong?
Replace `staging` or `patchBuilding` contexts with `normal`, and their `Secondary` variants with `normalSecondary`; review bindings for the broader main view. Removed contexts now fail config validation.
Wrong?
For interactive staging in rendered output, update Delta or Diff-so-fancy to a version supporting OSC 1717. Difftastic needs the custom build linked in the release notes.
Read the evidence
Wrong?
Fix invalid templates in `git.diffRenderers[].command` before launch: renderer commands are now parsed and evaluated as Go templates during config loading.
Wrong?
Stacked branches stay in stack order when committer dates tie. Divergence caused only by a rewritten upstream is shown in dim yellow.
Read the evidence
Wrong?
`git.autoForwardBranches` can now advance branches checked out in another worktree, unless it has tracked-file changes or is rebasing or bisecting.
Read the evidence
Wrong?
Selected text is bold by default; selection backgrounds adapt to the terminal background. Set `gui.theme.selectedLineFgColor: [default]` to keep selected text unbolded.
Read the evidence
Wrong?
`gui.commitGraphStyle: auto` selects detailed branch-drawing symbols in kitty and Ghostty, and classic rendering elsewhere; other compatible terminals or fonts can opt into `detailed`.
Read the evidence
Wrong?
Copied commits remain available after switching worktrees or repositories.
Read the evidence
Wrong?
`Esc` is handled without the significant delay introduced by the terminal input regression.
Read the evidence
Wrong?
A custom command whose `context` names a context that does not exist is now refused at config load with an error, instead of crashing later.
Wrong?
lazygit migrates these to `git.diffRenderers` and `cycleDiffRenderers` by rewriting the config file and stops with an error if it cannot write it; update a read-only config by hand.
Read the evidence
Wrong?
Submitting from the description editor is now `ctrl-enter` (`cmd-enter` on Mac), which not every terminal supports; to keep the old key, set `keybinding.universal.confirmInEditor: [<alt+enter>, <ctrl+s>]`.
Read the evidence
Wrong?
File trees now sort files and folders together (`gui.fileTreeSortOrder: mixed`, was folders first); set it back to keep the old order.
Wrong?
In the files and commit files views, `/` now filters the list by full path instead of searching it; actions on a directory apply only to the filtered files.
Wrong?
lazygit release history 14
Remove a submodule in a linked worktree without breaking its counterpart in the main worktree.
Details
Submodule removal now uses the linked worktree's own Git directory. Lazygit filters unsafe entries in `.gitmodules` and recognizes section headers and keys only at the start of a line.
Also: Submodules with unsafe names or paths are ignored; commented-out submodule entries and URLs containing `path=` are parsed correctly.
Available in the v0.66.3 release; requires Git.
Seeded by @iluxav with Codex
Read the evidence
- jesseduffield/lazygit/releases/tag/v0.66.3
- jesseduffield/lazygit/blob/v0.66.3/pkg/integration/tests/submodule/remove_in_linked_workt…
- jesseduffield/lazygit/blob/v0.66.3/pkg/commands/git_commands/submodule.go
- jesseduffield/lazygit/blob/v0.66.3/pkg/commands/git_commands/submodule_test.go
- jesseduffield/lazygit/compare/v0.66.2...v0.66.3
with v0.66.1
Inspect nested repositories and leftover submodule directories before discarding them.
Details
The files panel labels nested repositories, removed submodules and worktrees, shows their status, and warns before discarding history or uncommitted changes. Unwrapped focused diffs support `H` and `L` scrolling; staging and diff navigation regressions are fixed.
Also: Scroll unwrapped diffs sideways, stage with custom diff prefixes, and open branch files in the correct worktree. Source builds now require Go 1.26.
Available in v0.66.2, including v0.66.1 changes. Requires Git; building from source requires Go 1.26.0 or newer.
Seeded by @iluxav with Codex
Read the evidence
- jesseduffield/lazygit/releases/tag/v0.66.2
- jesseduffield/lazygit/blob/v0.66.2/pkg/i18n/english.go
- jesseduffield/lazygit/blob/v0.66.2/pkg/gui/controllers/files_controller.go
- jesseduffield/lazygit/releases/tag/v0.66.1
- jesseduffield/lazygit/blob/v0.66.1/pkg/commands/git_commands/diff.go
- jesseduffield/lazygit/blob/v0.66.1/docs/Config.md
- jesseduffield/lazygit/blob/v0.66.2/pkg/gocui/gui.go
- jesseduffield/lazygit/blob/v0.66.2/go.mod
Stage or unstage hunks and lines directly in the main diff view.
Details
The focused main diff replaces the staging and patch-building panels. Stack push/pull prompts, terminal-aware themes and detailed commit graphs accompany configuration migrations and validation changes.
Also: Synchronize stacked branches, adapt colors to dark or light terminals, and push or delete multiple tags.
Available in v0.66.0. Interactive custom-rendered diffs need OSC 1717 support; update Delta or Diff-so-fancy. Difftastic support requires the build linked in the release notes.
Seeded by @iluxav with Codex
Read the evidence
- jesseduffield/lazygit/blob/v0.66.0/README.md
- jesseduffield/lazygit/releases/tag/v0.66.0
- jesseduffield/lazygit/blob/v0.66.0/pkg/config/app_config.go
- jesseduffield/lazygit/blob/v0.66.0/pkg/config/user_config_validation.go
- jesseduffield/lazygit/blob/v0.66.0/docs/Stacked_Branches.md
- jesseduffield/lazygit/blob/v0.66.0/docs/Config.md
Use Escape without the long input delay affecting some terminals.
Details
Escape handling fixes a terminal input regression. The rebase editor child process no longer loads or migrates the user configuration.
Also: Rebasing a dotfiles repository no longer triggers config migration from the rebase editor child process.
Available in the v0.65.1 release.
Seeded by @iluxav with Codex
Filter the keybindings and recent repos menus just by typing.
Details
Typing in the keybindings and recent repos menus filters them; worktrees can be filtered by branch name; the window looks inactive when unfocused. A custom command with an unknown `context` name is now rejected when the config loads.
v0.65.0.
Seeded by @iluxav with Claude Code
Reorder commits by dragging them with the mouse.
Details
Drag commits or rebase todos to move them, and drag to select a range. `git.pagers` is renamed `git.diffRenderers` with a `type` field (`stdinFilter`, `extDiff`, `rawGit`) and one `command` field; existing configs are rewritten automatically.
Also: The branches list shows a GitHub PR's combined checks state.
v0.64.0.
Seeded by @iluxav with Claude Code
Rearrange, hide or regroup lazygit's side panels.
Details
New `gui.sidePanels` option to reorder, hide and regroup panels and tabs, and `gui.shrinkSidePanelsToContent`. direnv environments load when switching repos or worktrees; external changes are picked up by polling; `<alt+shift+c>` edits the config file.
v0.63.0; direnv support works when direnv is installed.
Seeded by @iluxav with Claude Code
Use git-flow-next with lazygit's git flow menu.
Details
Keybindings accept any modifier combination (`<ctrl+alt+shift+x>`) and several keys each; the documented syntax is now `<ctrl+a>` (the older `<c-a>` still works). git-flow-next and GitHub Enterprise pull requests are supported. Groups v0.62.0 and v0.62.1.
Also: `<alt+up>`/`<alt+down>` move commits; the commit graph uses more widely supported symbols.
v0.62.1.
Seeded by @iluxav with Claude Code
See which branches have a GitHub pull request, and whether it is open, closed or merged.
Details
With `gh` installed and logged in, branches with a pull request show a colored PR icon, and `shift-G` opens it. File trees now mix files and folders by default (`gui.fileTreeSortOrder: mixed`).
v0.61.0; the PR icons need `gh auth login`.
Seeded by @iluxav with Claude Code
Filter the file lists by path as you type, and stage or diff only what the filter shows.
Details
Typing a filter in the files and commit files views now filters by full path instead of searching; staging, diffs and discards apply only to the visible files. Lines can be removed from a custom patch directly.
v0.60.0.
Seeded by @iluxav with Claude Code
Open pull requests for repositories hosted on Codeberg.
Details
Codeberg is a supported hosting service for opening pull requests and commits. The merge conflict menu's keep item is on `k` again. Custom command menu prompts take custom keybindings.
v0.58.0.
Seeded by @iluxav with Claude Code
Add a fork as a remote by typing just its owner's name.
Details
A command adds a fork remote by replacing the owner in the origin URL, and can check out a branch from it. Switching repos triggers a background fetch at once.
v0.57.0.
Seeded by @iluxav with Claude Code
Resolve every conflict in chosen files as ours, theirs or both from a merge menu, without an external tool.
Details
`M` on a conflicted file now opens a merge options menu (ours, theirs, union, or the external merge tool); a no-ff merge option; several pagers in `git.pagers`, cycled with `|`.
Also: Checkout of the previous branch gives clearer feedback; `gui.skipSwitchWorktreeOnCheckoutWarning`.
v0.56.0.
Seeded by @iluxav with Claude Code
Starting point
Do the hard parts of git, from staging single lines to interactive rebase, with one key each in a terminal UI.
Details
Starting point: a terminal UI for git with panels for files, branches, commits and stash, run with `lazygit`.
Binary releases, Homebrew, most Linux package managers, or `go install`. Needs git.
Seeded by @iluxav with Claude Code