A simple terminal UI for git commands
[](https://github.com/jesseduffield/lazygit/releases) [](https://goreportcard.com/report/github.com/jesseduffield/lazygit) [](https://app.codacy.com/gh/jesseduffield/lazygit/dashboard?utm_source=gh&utm_medium=referral&utm_content=&utm_campaign=Badge_grade) [](https://app.codacy.com/gh/jesseduffield/lazygit/dashboard?utm_source=gh&utm_medium=referral&utm_content=&utm_campaign=Badge_coverage) [](https://golangci-lint.run/) [](https://github.com/jesseduffield/lazygit/releases/latest) [](https://formulae.brew.sh/formula/lazygit)
## Sponsors
Maintenance of this project is made possible by all the contributors and sponsors. If you'd like to sponsor this project and have your avatar or company logo appear below click here. 💙
## Elevator Pitch
Rant time: You've heard it before, git is _powerful_, but what good is that power when everything is so damn hard to do? Interactive rebasing requires you to edit a goddamn TODO file in your editor? _Are you kidding me?_ To stage part of a file you need to use a command line program to step through each hunk and if a hunk can't be split down any further but contains code you don't want to stage, you have to edit an arcane patch file _by hand_? _Are you KIDDING me?!_ Sometimes you get asked to stash your changes when switching branches only to realise that after you switch and unstash that there weren't even any conflicts and it would have been fine to just checkout the branch directly? _YOU HAVE GOT TO BE KIDDING ME!_
If you're a mere mortal like me and you're tired of hearing how powerful git is when in your daily life it's a powerful pain in your ass, lazygit might be for you.
## Table of contents
- [Sponsors](#sponsors)
- [Elevator Pitch](#elevator-pitch)
- [Table of contents](#table-of-contents)
- [Features](#features)
- [Stage individual lines](#stage-individual-lines)
- [Interactive Rebase](#interactive-rebase)
- [Cherry-pick](#cherry-pick)
- [Bisect](#bisect)
- [Nuke the working tree](#nuke-the-working-tree)
- [Amend an old commit](#amend-an-old-commit)
- [Filter](#filter)
- [Invoke a custom command](#invoke-a-custom-command)
- [Worktrees](#worktrees)
- [Rebase magic (custom patches)](#rebase-magic-custom-patches)
- [Rebase from marked base commit](#rebase-from-marked-base-commit)
- [Undo](#undo)
- [Commit graph](#commit-graph)
- [Compare two commits](#compare-two-commits)
- [Tutorials](#tutorials)
- [Installation](#installation)
- [Binary Releases](#binary-releases)
- [Dev container](#dev-container-feature)
- [Homebrew](#homebrew)
- [MacPorts](#macports)
- [Void Linux](#void-linux)
- [Scoop (Windows)](#scoop-windows)
- [gah (Linux and Mac OS)](#gah-linux-and-mac-os)
- [Arch Linux](#arch-linux)
- [Fedora / Amazon Linux 2023 / CentOS Stream](#fedora--amazon-linux-2023--centos-stream)
- [Fedora / RHEL Derivatives (Terra)](#fedora--rhel-derivatives-terra)
- [Solus Linux](#solus-linux)
- [Debian and Ubuntu](#debian-and-ubuntu)
- [Funtoo Linux](#funtoo-linux)
- [Gentoo Linux](#gentoo-linux)
- [openSUSE](#opensuse)
- [NixOS](#nixos)
- [Flox](#flox)
- [FreeBSD](#freebsd)
- [Termux](#termux)
- [Conda](#conda)
- [Go](#go)
- [Chocolatey (Windows)](#chocolatey-windows)
- [Winget (Windows 10 1709 or later)](#winget-windows-10-1709-or-later)
- [Manual](#manual)
- [Usage](#usage)
- [Keybindings](#keybindings)
- [Changing Directory On Exit](#changing-directory-on-exit)
- [Undo/Redo](#undoredo)
- [Configuration](#configuration)
- [Custom Pagers](#custom-pagers)
- [Custom Commands](#custom-commands)
- [Git flow support](#git-flow-support)
- [Contributing](#contributing)
- [Debugging Locally](#debugging-locally)
- [Donate](#donate)
- [FAQ](#faq)
- [What do the commit colors represent?](#what-do-the-commit-colors-represent)
- [Shameless Plug](#shameless-plug)
- [Alternatives](#alternatives)
Lazygit is not my fulltime job but it is a hefty part time job so if you want to support the project please consider [sponsoring me](https://github.com/sponsors/jesseduffield)
## Features
> **Note:** For the best experience with animated demonstrations, view this README on [GitHub](https://github.com/jesseduffield/lazygit#features). The feature descriptions below include detailed step-by-step instructions that work offline.
### Stage individual lines
Press space on the selected line to stage it, or press `v` to start selecting a range of lines. You can also press `a` to select the entirety of the current hunk.
**How it works:**
1. Navigate to the "Files" panel (main panel shows unstaged changes)
2. Press `` on a file to view its diff
3. Use arrow keys to navigate to specific lines
4. Press `` to stage/unstage the selected line
5. Press `v` to enter visual mode and select a range of lines with arrow keys
6. Press `` on a selected range to stage all lines in that range
7. Press `a` to stage the entire current hunk
### Interactive Rebase
Press `i` to start an interactive rebase. Then squash (`s`), fixup (`f`), drop (`d`), edit (`e`), move up (`ctrl+k`) or move down (`ctrl+j`) any of TODO commits, before continuing the rebase by bringing up the rebase options menu with `m` and then selecting `continue`.
You can also perform any these actions as a once-off (e.g. pressing `s` on a commit to squash it) without explicitly starting a rebase.
**How it works:**
1. Navigate to the "Commits" panel
2. Press `i` to start an interactive rebase (this shows a list of commits from HEAD to the merge base)
3. Navigate to a commit and press:
- `s` to squash it (combine with the previous commit, keeping both commit messages)
- `f` to fixup it (combine with the previous commit, discarding this commit's message)
- `d` to drop it (remove the commit entirely)
- `e` to edit it (stop at this commit during rebase)
- `ctrl+k` to move it up (swap with the commit above)
- `ctrl+j` to move it down (swap with the commit below)
4. Use `shift+down` or `shift+up` to select a range of commits
5. Press `m` to open the rebase options menu
6. Select "continue" to apply the rebase
**Quick actions:** You can also press `s` or `f` directly on any commit to squash/fixup without starting an explicit rebase.
### Cherry-pick
Press `shift+c` on a commit to copy it and press `shift+v` to paste (cherry-pick) it.
**How it works:**
1. Navigate to the "Commits" panel in the branch containing the commit you want
2. Navigate to the specific commit you want to cherry-pick
3. Press `shift+c` to copy (mark) the commit
4. Switch to the target branch (using the branches panel or checkout)
5. Press `shift+v` to paste (cherry-pick) the copied commit onto the current branch
6. Resolve any conflicts if necessary
7. Multiple commits can be copied and pasted in sequence
### Bisect
Press `b` in the commits view to mark a commit as good/bad in order to begin a git bisect.
**How it works:**
1. Navigate to the "Commits" panel
2. Find a commit where a bug was introduced (you know the current commit is "bad")
3. Find an older commit where the bug didn't exist (you know this commit is "good")
4. Press `b` on a commit to mark it:
- Select "mark as bad" for commits that have the bug
- Select "mark as good" for commits that don't have the bug
5. Git will automatically narrow down the range by checking commits in between
6. Continue marking commits as good/bad until git identifies the problematic commit
7. Press `b` and select "reset bisect" to end the bisect session
### Nuke the working tree
For when you really want to just get rid of anything that shows up when you run `git status` (and yes that includes dirty submodules) [kidpix style](https://www.youtube.com/watch?v=N4E2B_k2Bss), press `shift+d` to bring up the reset options menu and then select the 'nuke' option.
**How it works:**
1. Press `shift+d` in the Files panel to open the reset options menu
2. Select "Nuke working tree" to completely clean the working directory
3. This will:
- Discard all unstaged changes
- Remove untracked files
- Reset dirty submodules
- Essentially restore the working tree to match the HEAD commit
4. Use with caution - this is destructive and cannot be easily undone
### Amend an old commit
Pressing `shift+a` on any commit will amend that commit with the currently staged changes (running an interactive rebase in the background).
**How it works:**
1. Stage the changes you want to add to an old commit (use the Files panel)
2. Navigate to the "Commits" panel
3. Find the commit you want to amend
4. Press `shift+a` on that commit
5. Lazygit will automatically:
- Start an interactive rebase
- Stop at the selected commit
- Amend it with your staged changes
- Continue the rebase
6. The commit is updated without affecting subsequent commits' messages
### Filter
You can filter a view with `/`. Here we filter down our branches view and then hit `enter` to view its commits.
**How it works:**
1. In any panel (Files, Branches, Commits, etc.), press `/` to open the filter input
2. Type your search text (e.g., branch name, commit message, file name)
3. The list will be filtered to show only matching items
4. Press `` to select a filtered item and view its details
5. Press `` to clear the filter and show all items
6. Filters work across all panels: branches, commits, files, remotes, tags, etc.
### Invoke a custom command
Lazygit has a very flexible [custom command system](docs/Custom_Command_Keybindings.md). In this example a custom command is defined which emulates the built-in branch checkout action.
**How it works:**
1. Custom commands are defined in your lazygit config file
2. They can be triggered with custom keybindings
3. Commands can operate on selected items (branches, commits, files)
4. In this demo, a custom command performs a branch checkout:
- Navigate to the Branches panel
- Select a branch
- Press the custom command keybinding
- Lazygit executes the defined git command
5. Custom commands support prompts, menu selections, and shell commands
### Worktrees
You can create worktrees to have multiple branches going at once without the need for stashing or creating WIP commits when switching between them. Press `w` in the branches view to create a worktree from the selected branch and switch to it.
**How it works:**
1. Navigate to the "Branches" panel
2. Select the branch you want to create a worktree for
3. Press `w` to open the worktree options menu
4. Select "Create worktree from branch"
5. Enter the path where the worktree should be created
6. Lazygit will:
- Create a new worktree directory
- Checkout the selected branch into that worktree
- Optionally switch to that worktree
7. You can work in multiple worktrees simultaneously without stashing
**Benefits:**
- Work on multiple branches simultaneously
- No need to stash changes when switching contexts
- Each worktree has its own working directory
- Share the same .git directory (saves space)
### Rebase magic (custom patches)
You can build a custom patch from an old commit and then remove the patch from the commit, split out a new commit, apply the patch in reverse to the index, and more.
In this example we have a redundant comment that we want to remove from an old commit. We hit `` on the commit to view its files, then `` on a file to focus the patch, then `` to add the comment line to our custom patch, and then `ctrl+p` to view the custom patch options; selecting to remove the patch from the current commit.
Learn more in the [Rebase magic Youtube tutorial](https://youtu.be/4XaToVut_hs).
**How it works (removing a line from an old commit):**
1. Navigate to the "Commits" panel
2. Press `` on the commit containing the line you want to modify
3. Press `` on the specific file to view its contents
4. Navigate to the line(s) you want to remove or change
5. Press `` to add those lines to a "custom patch" (a temporary holding area)
6. Press `ctrl+p` to open the custom patch options menu
7. Select "Remove patch from commit" - this removes those lines from that commit
8. Lazygit performs an interactive rebase in the background to rewrite history
**Other custom patch options:**
- Apply patch in reverse (revert the changes)
- Create a new commit from the patch
- Copy patch to clipboard
- Pull patch into index (stage the changes)
### Rebase from marked base commit
Say you're on a feature branch that was itself branched off of the develop branch, and you've decided you'd rather be branching off the master branch. You need a way to rebase only the commits from your feature branch. In this demo we check to see which was the last commit on the develop branch, then press `shift+b` to mark that commit as our base commit, then press `r` on the master branch to rebase onto it, only bringing across the commits from our feature branch. Then we push our changes with `shift+p`.
**How it works:**
1. Navigate to the "Commits" panel on your feature branch
2. Find the commit that represents the base of your feature branch (e.g., the last commit from develop before you started your feature)
3. Press `shift+b` on that commit to mark it as the "base commit"
4. Navigate to the "Branches" panel (or Remotes panel)
5. Select the branch you want to rebase onto (e.g., master)
6. Press `r` to rebase onto that branch
7. Lazygit will only rebase the commits after your marked base commit
8. Press `shift+p` to push the rebased commits
**Use cases:**
- Rebase feature branch onto a different upstream branch
- Move commits to a clean base
- Avoid rebasing commits from other branches
### Undo
You can undo the last action by pressing `z` and redo with `ctrl+z`. Here we drop a couple of commits and then undo the actions.
Undo uses the reflog which is specific to commits and branches so we can't undo changes to the working tree or stash.
[More info](/docs/Undoing.md)
**How it works:**
1. Press `z` to undo the last action (undo goes back through the reflog)
2. Press `ctrl+z` to redo (undo an undo)
3. Works for most git operations:
- Commits
- Branch operations (create, delete, checkout)
- Rebase operations
- Cherry-pick operations
- Reset operations
4. Undo history is stored in the git reflog
5. Note: Cannot undo working tree changes (unstaged files) or stash operations
**When to use:**
- Accidentally deleted a branch
- Made a wrong commit
- Rebase went wrong
- Cherry-pick in the wrong place
### Commit graph
When viewing the commit graph in an enlarged window (use `+` and `_` to cycle screen modes), the commit graph is shown. Colours correspond to the commit authors, and as you navigate down the graph, the parent commits of the selected commit are highlighted.
**How it works:**
1. Press `+` to enlarge the main panel (cycles through screen modes)
2. The commits view shows a visual graph of commit history
3. Each commit is represented as a node in the graph
4. Different colors represent different authors
5. Lines show the parent-child relationships between commits
6. As you navigate through commits, parent commits are highlighted
7. Press `_` to reduce the panel size
**Visual features:**
- Branch lines show merge points
- Author colors help track who wrote what
- Navigate complex history visually
- See where branches diverge and merge
### Compare two commits
If you press `shift+w` on a commit (or branch/ref) a menu will open that allows you to mark that commit so that any other commit you select will be diffed against it. Once you've selected the second commit, you'll see the diff in the main view and if you press `` you'll see the files of the diff. You can press `shift+w` to view the diff menu again to see options like reversing the diff direction or exiting diff mode. You can also exit diff mode by pressing ``.
**How it works:**
1. Navigate to the "Commits" panel
2. Press `shift+w` on a commit to mark it as the "base" for comparison
3. Select "Mark as base for comparison" from the menu
4. Navigate to another commit
5. The main view now shows the diff between the two commits
6. Press `` to see the specific file changes in the diff
7. Press `shift+w` again to see options:
- Reverse the diff direction (swap base and comparison)
- Exit diff mode
- Copy diff to clipboard
8. Press `` to exit diff mode
**Use cases:**
- Compare two branches
- See what changed between two versions
- Review changes before a merge
- Find where a bug was introduced
## Tutorials
[
](https://youtu.be/CPLdltN7wgE)
- [15 Lazygit Features in 15 Minutes](https://youtu.be/CPLdltN7wgE)
- [Basics Tutorial](https://youtu.be/VDXvbHZYeKY)
- [Rebase Magic Tutorial](https://youtu.be/4XaToVut_hs)
## Installation
[](https://repology.org/project/lazygit/versions)
_Most of the above packages are maintained by third parties so be sure to vet them yourself and confirm that the maintainer is a trustworthy looking person who attends local sports games and gives back to their communities with barbeque fundraisers etc_
### Binary Releases
For Windows, Mac OS(10.12+) or Linux, you can download a binary release [here](../../releases).
### Dev container feature
If you want to use lazygit in e.g. one of your GitHub Codespaces, there is a third-party [dev container feature](https://github.com/GeorgOfenbeck/features/tree/main/src/lazygit-linuxbinary) based on the binary releases mentioned above.
### Homebrew
It works with Linux, too.
```sh
brew install lazygit
```
### MacPorts
Latest version built from github releases.
Tap:
```
sudo port install lazygit
```
### Void Linux
Packages for Void Linux are available in the distro repo
They follow upstream latest releases
```sh
sudo xbps-install -S lazygit
```
### Scoop (Windows)
You can install `lazygit` using [scoop](https://scoop.sh/). It's in the `extras` bucket:
```sh
# Add the extras bucket
scoop bucket add extras
# Install lazygit
scoop install lazygit
```
### gah (Linux and Mac OS)
You can install `lazygit` using [gah](https://github.com/marverix/gah/):
```sh
gah install lazygit
```
### Arch Linux
Packages for Arch Linux are available via pacman and AUR (Arch User Repository).
There are two packages. The stable one which is built with the latest release
and the git version which builds from the most recent commit.
- Stable: `sudo pacman -S lazygit`
- Development:
Instruction of how to install AUR content can be found here:
### Fedora / Amazon Linux 2023 / CentOS Stream
Packages for Fedora, Amazon Linux 2023 and CentOS Stream are available via
[Copr](https://copr.fedorainfracloud.org/coprs/dejan/lazygit/) (Cool Other Package Repo).
```sh
sudo dnf copr enable dejan/lazygit
sudo dnf install lazygit
```
These packages are built using the RPM spec file located here: https://codeberg.org/dejan/rpm-lazygit
You should be able to build RPMs for Fedora 41 or older, and other Fedora derivatives using the
SRPM (Source RPM) file that you can grab from the latest COPR build.
#### Fedora / RHEL Derivatives (Terra)
Packages for Fedora and RHEL derivatives are also available from the [Terra Repository](https://terra.fyralabs.com/).
```sh
sudo dnf install --nogpgcheck --repofrompath 'terra,https://repos.fyralabs.com/terra$releasever' terra-release
sudo dnf install lazygit
```
(Install guide for Atomic/EL can be found on their [README](https://github.com/terrapkg/packages/pull/9747))
Terra also has `lazygit-doc`, which contains the contents of the [docs](https://github.com/jesseduffield/lazygit/tree/master/docs) folder.
### Solus Linux
```sh
sudo eopkg install lazygit
```
### Debian and Ubuntu
For **Debian 13 "Trixie", Sid**, and later, or **Ubuntu 25.10 "Questing Quokka"** and later:
```sh
sudo apt install lazygit
```
For **Debian 12 "Bookworm", Ubuntu 25.04 "Plucky Puffin"** and earlier:
```sh
LAZYGIT_VERSION=$(curl -s "https://api.github.com/repos/jesseduffield/lazygit/releases/latest" | \grep -Po '"tag_name": *"v\K[^"]*')
curl -Lo lazygit.tar.gz "https://github.com/jesseduffield/lazygit/releases/download/v${LAZYGIT_VERSION}/lazygit_${LAZYGIT_VERSION}_Linux_x86_64.tar.gz"
tar xf lazygit.tar.gz lazygit
sudo install lazygit -D -t /usr/local/bin/
```
Verify the correct installation of lazygit:
```sh
lazygit --version
```
### Funtoo Linux
Funtoo Linux has an autogenerated lazygit package in [dev-kit](https://github.com/funtoo/dev-kit/tree/1.4-release/dev-vcs/lazygit):
```sh
sudo emerge dev-vcs/lazygit
```
### Gentoo Linux
Lazygit is not (yet) in main Gentoo portage, however an ebuild is available in [GURU overlay](https://github.com/gentoo-mirror/guru/tree/master/dev-vcs/lazygit)
You can either add the overlay to your system and install lazygit as usual:
```sh
sudo eselect repository enable guru
sudo emaint sync -r guru
sudo emerge dev-vcs/lazygit
```
### openSUSE
The lazygit package is currently built in [devel:languages:go/lazygit](https://build.opensuse.org/package/show/devel:languages:go/lazygit).
To install lazygit on openSUSE Tumbleweed run:
```sh
sudo zypper ar https://download.opensuse.org/repositories/devel:/languages:/go/openSUSE_Factory/devel:languages:go.repo
sudo zypper ref && sudo zypper in lazygit
```
To install lazygit on openSUSE Leap run:
```sh
source /etc/os-release
sudo zypper ar https://download.opensuse.org/repositories/devel:/languages:/go/$VERSION_ID/devel:languages:go.repo
sudo zypper ref && sudo zypper in lazygit
```
### NixOS
#### Using lazygit from nixpkgs
On NixOS, lazygit is packaged with nix and distributed via nixpkgs.
You can try lazygit without installing it with:
```sh
nix-shell -p lazygit
# or with flakes enabled
nix run nixpkgs#lazygit
```
Or you can add lazygit to your `configuration.nix` using the `environment.systemPackages` option.
More details can be found via NixOS search [page](https://search.nixos.org/).
#### Using the official lazygit flake
This repository includes a nix flake that provides the latest development version and additional development tools:
**Run lazygit directly from the repository:**
```sh
nix run github:jesseduffield/lazygit
# or from a local clone
nix run .
```
**Build lazygit from source:**
```sh
nix build github:jesseduffield/lazygit
# or from a local clone
nix build .
```
**Development environment:**
For contributors, the flake provides a development shell with Go toolchain, development tools, and dependencies:
```sh
nix develop github:jesseduffield/lazygit
# or from a local clone
nix develop
```
The development shell includes:
- Go toolchain
- git and make
- Proper environment variables for development
**Using in other flakes:**
The flake also provides an overlay for easy integration into other flake-based projects:
```nix
{
inputs.lazygit.url = "github:jesseduffield/lazygit";
outputs = { self, nixpkgs, lazygit }: {
# Use the overlay
nixpkgs.overlays = [ lazygit.overlays.default ];
};
}
```
### Flox
Lazygit can be installed into a Flox environment as follows.
```sh
flox install lazygit
```
More details about Flox can be found on [their website](https://flox.dev/).
### FreeBSD
```sh
pkg install lazygit
```
### Termux
```sh
apt install lazygit
```
### Conda
Released versions are available for different platforms, see
```sh
conda install -c conda-forge lazygit
```
### Go
```sh
go install github.com/jesseduffield/lazygit@latest
```
Please note:
If you get an error claiming that lazygit cannot be found or is not defined, you
may need to add `~/go/bin` to your $PATH (macOS/Linux), or `%HOME%\go\bin`
(Windows). Not to be mistaken for `C:\Go\bin` (which is for Go's own binaries,
not apps like lazygit).
### Chocolatey (Windows)
You can install `lazygit` using [Chocolatey](https://chocolatey.org/):
```sh
choco install lazygit
```
### Winget (Windows 10 1709 or later)
You can install `lazygit` using the `winget` command in the Windows Terminal with the following command:
```powershell
winget install -e --id=JesseDuffield.lazygit
```
### Manual
You'll need to [install Go](https://golang.org/doc/install)
```
git clone https://github.com/jesseduffield/lazygit.git
cd lazygit
go install
```
You can also use `go run main.go` to compile and run in one go (pun definitely intended)
## Usage
Call `lazygit` in your terminal inside a git repository.
```sh
$ lazygit
```
If you want, you can
also add an alias for this with `echo "alias lg='lazygit'" >> ~/.zshrc` (or
whichever rc file you're using).
### Keybindings
You can check out the list of keybindings [here](/docs/keybindings).
### Changing Directory On Exit
If you change repos in lazygit and want your shell to change directory into that repo on exiting lazygit, add this to your `~/.zshrc` (or other rc file):
```
lg()
{
export LAZYGIT_NEW_DIR_FILE=~/.lazygit/newdir
lazygit "$@"
if [ -f $LAZYGIT_NEW_DIR_FILE ]; then
cd "$(cat $LAZYGIT_NEW_DIR_FILE)"
rm -f $LAZYGIT_NEW_DIR_FILE > /dev/null
fi
}
```
Then `source ~/.zshrc` and from now on when you call `lg` and exit you'll switch directories to whatever you were in inside lazygit. To override this behaviour you can exit using `shift+Q` rather than just `q`.
### Undo/Redo
See the [docs](/docs/Undoing.md)
## Configuration
Check out the [configuration docs](docs/Config.md).
### Custom Pagers
See the [docs](docs/Custom_Pagers.md)
### Custom Commands
If lazygit is missing a feature, there's a good chance you can implement it yourself with a custom command!
See the [docs](docs/Custom_Command_Keybindings.md)
### Git flow support
Lazygit supports [Gitflow](https://github.com/nvie/gitflow) if you have it installed. To understand how the Gitflow model works check out Vincent Driessen's original [post](https://nvie.com/posts/a-successful-git-branching-model/) explaining it. To view Gitflow options from within Lazygit, press `i` from within the branches view.
## Contributing
We love your input! Please check out the [contributing guide](CONTRIBUTING.md).
For contributor discussion about things not better discussed here in the repo, join the [discord channel](https://discord.gg/ehwFt2t4wt)
Check out this [video](https://www.youtube.com/watch?v=kNavnhzZHtk) walking through the creation of a small feature in lazygit if you want an idea of where to get started.
### Debugging Locally
Run `lazygit --debug` in one terminal tab and `lazygit --logs` in another to view the program and its log output side by side
## Donate
If you would like to support the development of lazygit, consider [sponsoring me](https://github.com/sponsors/jesseduffield) (github is matching all donations dollar-for-dollar for 12 months)
## FAQ
### What do the commit colors represent?
- Green: the commit is included in the master branch
- Yellow: the commit is not included in the master branch
- Red: the commit has not been pushed to the upstream branch
## Shameless Plug
If you want to see what I (Jesse) am up to in terms of development, follow me on
[twitter](https://twitter.com/DuffieldJesse) or check out my [blog](https://jesseduffield.com/)
## Alternatives
If you find that lazygit doesn't quite satisfy your requirements, these may be a better fit:
- [GitUI](https://github.com/Extrawurst/gitui)
- [tig](https://github.com/jonas/tig)
- [GitArbor TUI](https://github.com/cadamsdev/gitarbor-tui)
