Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
git-branchless
Suite of git extensions for a branchless, patch-stack workflow: smartlog, undo, restack, in-memory rebases, revsets; aimed at monorepo-scale work.
v0.11.1 released 2026-05-21; commits through 2026-10-24 (GitHub API). (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is it mainly sustained? individual with revenue (paid app, tier, ads, or donations) (0% of 16 others)
- Which layer of the stack does it mainly replace? the git client and local workflow, on top of git (10% of 20 others)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? yes, the workflow is built around stacks (20% of 15 others)
- What size of project is it designed for? very large monorepos or large binary assets (21% of 19 others)
- Is code review part of the product? no, it hands off to an external forge's review (e.g. GitHub pull requests) (11% of 19 others)
What it shares with most of the community
- Is it actively maintained? active (90% of 20 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (53% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (67% of 18 others)
- Who is it for? developers (90% of 20 others)
- How does it relate to git repositories? built on git: reads and writes git repositories directly (53% of 19 others)
- Can you commit, branch, and read history with no network connection? yes (94% of 17 others)
- Is it designed with AI coding agents in mind? no (65% of 20 others)
- What is the basic unit of history? (pick the most specific that applies) snapshots (commits) with no identity that survives a rewrite (74% of 19 others)
- How are merge conflicts mainly handled? must be resolved before the merge or commit completes (65% of 17 others)
Nearest neighbors
- Game of Trees (Got) 76% of 17 shared answers match
- Sapling 76% of 17 shared answers match
- Gitea 65% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) Apache-2.0 (GitHub API). | source 2026-10-25 |
| How is it mainly sustained? | stands apart individual with revenue (paid app, tier, ads, or donations) Single maintainer funded by GitHub Sponsors donations. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Local git extensions; no account. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | git (repository format and protocol) Extensions over git. | source 2026-10-26 |
| How does it relate to git repositories? | built on git: reads and writes git repositories directly | source 2026-10-25 |
| Where does the authoritative copy of a project live? | every clone is a full peer; servers are optional | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | yes | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | no | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | stands apart the git client and local workflow, on top of git | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | snapshots (commits) with no identity that survives a rewrite Git commits; tracks rewrites in an event log to power undo. | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | stands apart yes, the workflow is built around stacks README: 'strong support for patch-stack workflows'. | source 2026-10-25 |
| How are merge conflicts mainly handled? | must be resolved before the merge or commit completes Git-style; speculative merges warn about conflicts ahead of time. | source 2026-10-25 |
| What size of project is it designed for? | stands apart very large monorepos or large binary assets Description: 'High-velocity, monorepo-scale workflow for Git'. | source 2026-10-25 |
| Is code review part of the product? | stands apart no, it hands off to an external forge's review (e.g. GitHub pull requests) git submit pushes to forges such as GitHub or Phabricator. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/arxanas/git-branchless · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.