Git branch management tool, built from the ground up for modern workflows
gitbutler.com »
Download for
macOS (Apple Silicon |
Intel) ·
Linux (AppImage |
deb)
~ Link for Windows will be added once a release is available. ~
GitButler is a git client that lets you work on multiple branches at the same time. It allows you to quickly organize file changes into separate branches while still having them applied to your working directory. You can then push branches individually to your remote, or directly create pull requests.
In a nutshell, it's a more flexible version of git add -p and git rebase -i, allowing you to efficiently multitask across branches.
GitButler keeps track of uncommitted changes in a layer on top of Git. Changes to files or parts of files can be grouped into what we call virtual branches. Whenever you are happy with the contents of a virtual branch, you can push it to a remote. GitButler makes sure that the state of other virtual branches is kept separate.
The branches that we know and love in Git are separate universes, and switching between them is a full context switch. GitButler allows you to work with multiple branches in parallel in the same working directory. This effectively means having the content of multiple branches available at the same time.
GitButler is aware of changes before they are committed. This allows it to keep a record of which virtual branch each individual diff belongs to. Effectively, this means that you can separate out individual branches with their content at any time to push them to a remote or to unapply them from your working directory.
And finally, while in Git it is preferable that you create your desired branch ahead of time, using GitButler you can move changes between virtual branches at any point during development.
We love Git. Our own @schacon has even published the Pro Git book. At the same time, Git's user interface hasn't been fundamentally changed for 15 years. While it was written for Linux kernel devs sending patches to each other over mailing lists, most developers today have different workflows and needs.
Instead of trying to fit the semantics of the Git CLI into a graphical interface, are starting with the developer workflow and mapping it back to Git.
GitButler is a Tauri-based application. Its UI is written in Svelte using TypeScript and its backend is written in Rust.
- Virtual Branches
- Organize work on multiple branches simultaneously, rather than constantly switching branches
- Automatically create new branches when needed
- Easy Commit Management
- Undo, Amend and Squash commits by dragging and dropping
- GitHub Integration
- Authenticate to GitHub to open Pull Requests, list branches and statuses and more
- Easy SSH Key Management
- GitButler can generate an SSH key to upload to GitHub automatically
- AI Tooling
- Automatically write commit messages based on your work in progress
- Automatically create descriptive branch names
- Commit Signing
- Easy commit signing with our generated SSH key
Say that while developing a feature, you encounter a bug that you wish to fix. It's often desirable that you ship the fix as a separate contribution (Pull request).
Using Git you can stash your changes and switch to another branch, where you can commit, and push your fix.
With GitButler you simply assign your fix to a separate virtual branch, which you can individually push (or directly create a PR). An additional benefit is that you can retain the fix in your working directory while waiting for CI and/or code review.
Say you want to test a branch from someone else for the purpose of code review.
Using Git trying out someone else's branch is a full context switch away from your own work. With GitButler you can apply and unapply (add / remove) any remote branch directly into your working directory.
You can find our end user documentation at: https://docs.gitbutler.com
If you have a bug or feature request, feel free to open an issue, or join our Discord server.
So you want to help out? Please check out the CONTRIBUTING.md document.
If you want to skip right to getting the code to actually compile, take a look at the DEVELOPMENT.md file.