💪 git-machete is a robust tool that simplifies your git workflows.

🦅 The bird's eye view provided by git-machete makes merges/rebases/push/pulls hassle-free even when multiple branches are present in the repository (master/develop, your topic branches, teammate's branches checked out for review, etc.).

🎯 Using this tool, you can maintain small, focused, easy-to-review pull requests with little effort.

👁 A look at a git machete status gives an instant answer to the questions:

• What branches are in this repository?
• What is going to be merged (rebased/pushed/pulled) and to what?

🚜 git machete traverse semi-automatically traverses the branches, helping you effortlessly rebase, merge, push and pull.

🔌 See also VirtusLab/git-machete-intellij-plugin — a port into a plugin for the IntelliJ Platform products, including PyCharm, WebStorm etc.

We provide a couple of alternative ways of installation. See PACKAGES.md for the full list.

git-machete requires Python >= 3.6. Python 2.x is no longer supported.

brew install git-machete

You need to have Python and pip installed from system packages.

For user-wide install:

pip install --user git-machete

Please verify that your PATH variable has ${HOME}/.local/bin/ included.

For system-wide install:

sudo -H pip install git-machete  # system-wide install

Tip: pass an extra -U flag to pip install to upgrade an already installed version.

conda install -c conda-forge git-machete

scoop install git-machete

Tip: check the guide on installing snapd if you don't have Snap support set up yet in your system.

sudo snap install --classic git-machete

It can also be installed via Ubuntu Software (simply search for git-machete).

Note: classic confinement is necessary to ensure access to the editor installed in the system (to edit e.g. .git/machete file or rebase TODO list).

Check Repology for the available distro-specific packages.

On macOS and most Linux distributions, you can install via Nix:

nix-channel --add https://nixos.org/channels/nixos-unstable unstable  # if you haven't set up any channels yet
nix-env -i git-machete

Note: since nixos-21.05, git-machete is included in the stable channels as well. The latest released version, however, is generally available in the unstable channel. Stable channels may lag behind; see repology for the current channel-package mapping.

The Pex tool (short for Python EXecutable) allows you to build "pex" files which are executable Python environments in a single file.

Assuming you have already installed the pex utility, you can build git-machete as a pex:

pex git-machete -m git_machete.bin:main -o git-machete

Then put the produced git-machete file somewhere on your PATH.

cd your-repo/
git machete discover

See and possibly edit the suggested layout of branches. Branch layout is always kept as a .git/machete text file, which can be edited directly or via git machete edit.

git machete status --list-commits

Green edge means the given branch is in sync with its parent.
Red edge means it is out of sync — parent has some commits that the given branch does not have.
Gray edge means that the branch is merged to its parent.

git machete traverse --fetch --start-from=first-root

Put each branch one by one in sync with its parent and remote tracking branch.

git machete advance

Useful for merging the child branch to the current branch in a linear fashion (without creating a merge commit).

Check out the given PRs into local branches, also traverse chain of pull requests upwards, adding branches one by one to git-machete and check them out locally as well:

git machete github checkout-prs [--all | --by=<github-login> | --mine | <PR-number-1> ... <PR-number-N>]
git machete gitlab checkout-mrs [--all | --by=<gitlab-login> | --mine | <MR-number-1> ... <MR-number-N>]

Create the PR/MR, using the upstream (parent) branch from .git/machete as the base:

git machete github create-pr [--draft]
git machete gitlab create-mr [--draft]

The entire chain of PRs/MRs will be posted in the PR/MR description (example for GitHub):

Note: for private repositories (or side-effecting operations like create-pr/create-mr on public repositories), a GitHub API token with repo access or a GitLab API token with api access is required. See the docs for github or gitlab for how to provide the token.

When git-machete is installed via Homebrew (and a few other supported package managers, see PACKAGES.md), shell completions should be installed automatically.
For other package managers (like pip), or when your shell doesn't pick up the Homebrew-installed completion, use the following:

Put the following into ~/.bashrc or ~/.bash_profile:

eval "$(git machete completion bash)"  # or, if it doesn't work:
source <(git machete completion bash)

Put the following into ~/.config/fish/config.fish:

git machete completion fish | source

Put the following into ~/.zshrc:

eval "$(git machete completion zsh)"  # or, if it doesn't work:
source <(git machete completion zsh)

No! It's all right, discover is based on an (imperfect) heuristic which usually yields branch layout close to what the user would expect. It still might not be perfect and — for example — declare branches to be children of main/develop instead of each other.

Just run git machete edit to fix the layout manually. If you're working on JetBrains IDEs, you can use git-machete IntelliJ plugin to have branch name completion when editing .git/machete file.

Also, consider git machete github checkout-prs or git machete gitlab checkout-mrs instead of git machete discover if you already have GitHub PRs/GitLab MRs opened.

Contrary to the popular misconception, git doesn't have a notion of "commits belonging to a branch". A branch is just a movable reference to a commit.

This makes it hard in general case to determine the range of commits that form the "unique history" of the given branch. There's an entire algorithm in git-machete for determining the fork point of the branch (i.e. the place after which the unique history of the branch starts).

One thing that you can do to help fork-point algorithm in its job, is to not delete local branches instantly after they're merged or discarded. They (or specifically, their reflogs) will be still useful for a while to determine fork points for other branches (and thus, the range of commits taken into rebase).

Also, you can always override fork point for a branch explicitly with git machete fork-point --override-to... command.

There are two commonly used ways to put a branch back in sync with its base (parent) branch:

1. rebase the branch onto its base branch
2. merge the base branch into the branch

While git-machete supports merging base branch (like main) to update the branch (git machete traverse --merge), this approach works poorly with stacked branches. You might end up with a very tangled history very quickly, and a non-trivial sequence of git cherry-picks might be needed to restore order.

That is why we recommend using rebase over merge for stacked branches. However, we still recommend using merge for the narrow case of backporting hotfixes.

We recommend merging PRs from the top-most (closest to the root branch, typically main or master). In other words, PR should only be merged when its base is a root branch.

This way, you don't end up with a big-ball-of-code PR at the end. Avoiding such "balls" is one of the main reasons for opening small PRs in the first place.

Due to the limitations of GitHub's PR model, it is not possible to cleanly create stacked PRs from forks. Generally, PRs need to be created in whatever repository the base branch lives.

Let's consider a hypothetical chain qux ➔ foo ➔ bar ➔ master, where master lives in the original repo and qux, bar, foo live in a fork. In such case, a PR for bar ➔ master will be opened in the original repo, as expected. The subsequent PRs (foo ➔ bar, qux ➔ foo), however, will have base branches from the fork — and hence they'll be opened in the fork instead of the original repo. This is usually undesirable, as there'll be no way to retarget these PRs to master (which lives in the original repo), and thus no way to merge them directly to master via GitHub.

The alternative is to always open the PRs directly to master in the original repo (even from the further branches), but this is also inconvenient as the range of commits would need to be narrowed down manually when viewing the PRs.

Find the docs at Read the Docs. You can also check git machete help and git machete help <command>.

For the excellent overview for the reasons to use small & stacked PRs, see Ben Congdon's blog post.

Take a look at git-machete reference blog post for a guide on how to use the tool.

The more advanced features like automated traversal, upstream inference and tree discovery are described in the second part of the series.

git-machete (since version 2.13.0) is compatible with git >= 1.8.0.

Contributions are welcome! See contributing guidelines for details.