Related tools

See the Architecture page for work related to the implementation of git-branchless.

Alternative tools:

• ~krobelus/git-branchstack: A tool which allows you to make all of your commits to one branch, and then automatically split them up into separate branches later based on their topic.
• git-stack: This tool helps you create stacked branches and keep them up-to-date.
• Stacked Git: This tool lets you efficiently manage a stack of patches alongside your regular work. In comparison, git-branchless encourages that you commit all of your work directly and manipulate those commits directly.
• Git Patch Stack: Similar to Stacked Git, specifically intended to support using a pull request workflow.
• Jujutsu: An experimental, Git-compatible VCS. Supports anonymous branches, undo, checked-in conflicts, auto-rebase. Uses a completely different CLI (jj instead of git) and does not work in a Git working copy, but can work as an alternative working copy (like git worktree).
• Sapling: Facebook's internal Mercurial fork with Git support added, and the original inspiration for many other tools here. Compatible with Git servers, but has its own local on-disk format.

Complementary tools:

• git-absorb/git-autofixup: These tools let you take your current changes, at the top of a stack, and intelligently "absorb" them into previous related changes in the same stack.
• git-revise: This tool lets you "efficiently update, split, and rearrange git commits" without touching the working copy.