Utiliser lazygit : installation, raccourcis, staging, commits, rebase interactif

Stager et committer dans un UI Git terminal, puis essayer un premier rebase interactif dans lazygit.

Tweaking a few files should not mean bouncing between git status, git add -p, and another editor. lazygit is a terminal UI for Git: status, staging, commits, branches, and interactive rebase in one place. Upstream repo: github.com/jesseduffield/lazygit.

Searchers looking for lazygit install keybindings stage commit interactive rebase want: install, learn panels and core keys, stage and commit, and a safe first interactive rebase. Key names follow lazygit’s official Keybindings — press ? in-app to verify your version.

Pour qui lazygit convient

Installer lazygit

1. 1

   macOS: Homebrew

   brew install lazygit, then lazygit --version.

2. 2

   Windows

   winget install JesseDuffield.lazygit or scoop install lazygit per current package names.

3. 3

   Linux

   Arch: sudo pacman -S lazygit. Other distros: distro packages, GitHub Releases binaries, or go install github.com/jesseduffield/lazygit@latest with Go installed.

4. 4

   First launch

   Run lazygit inside a repo root. Outside a repo it errors — cd into a project or git init first.

Panneaux et raccourcis

lazygit splits Status, Files, Branches, Commits, and more. Keys 1–5 often focus panels — confirm with ? on your build.

Stager et committer

1. 1

   Open the repo

   cd your-repo && lazygit. Files panel lists modified and untracked paths.

2. 2

   Read the diff

   Select a file, press Enter for the diff.

3. 3

   Stage

   Space on a file in the list; for partial stages use hunk actions in the diff/patch view (see help for “stage”).

4. 4

   Commit

   Press c, type the message, confirm.

5. 5

   Optional push

   P to push; new branches may prompt for upstream — follow on-screen choices.

cd ~/projects/my-app
lazygit
# Files → Space → c → message → P

Rebase interactif – introduction

Interactive rebase rewrites local history — squash, reorder, reword. Avoid rebasing shared branches others already built on unless your team allows it.

1. 1

   Commits panel

   Focus Commits (number keys / Tab) to see branch history.

2. 2

   Start rebase

   Select the base commit (or use branch actions per docs), press i for interactive rebase. A todo list of pick/squash/fixup appears.

3. 3

   Edit the todo

   Move the cursor; toggle actions with keys shown in ? (pick, squash, fixup, drop).

4. 4

   Confirm & fix conflicts

   lazygit runs the rebase. On conflicts, resolve in Files/diff views and continue rebase via menu or keys in help.

5. 5

   Before push

   Rewritten history may need force-with-lease. lazygit surfaces push options — do not force-push shared mainlines blindly.

Practice on a throwaway branch and git branch backup-before-rebase before your first squash via i.

Align release steps in lazygit; for a shared flow diagram, open a browser room from the wbroom homepage — create and join a room; for terminal multiplexing see tmux guide.

À vérifier