View changes from public GitHub pull requests, comparisons, commits, diffs, and patches with DiffsHub.
Stacking
Manage pull requests and code changes with a stacked workflow in Stacking.
About Stacking
Stacking is an informational site explaining the stacked pull request workflow: instead of waiting for a PR to be reviewed and merged before starting dependent work, a developer puts the first change up for review, creates a dependent branch, and continues building on top of it. The site describes how this parallelizes development and code review, why stacks must be recursively rebased when an upstream change lands, and why doing that by hand with the Git CLI is time-consuming.
The site does not provide its own stacking tool. It points readers to third-party options for GitHub and other systems (Graphite, ghstack, git town, Sapling and spr) and notes that Git's --update-refs option reduces the number of rebases needed, though parts of the process, such as opening PRs, remain manual. It states the approach works in almost any repository and is independent of language and of whether a team rebases or merges.
Key features
- Explains stacked PRs, stacked diffs and stacked changes
- Describes parallelizing development and review to avoid blocking on merges
- Covers recursive rebasing needed when an upstream stack change lands
- Lists third-party stacking tools: Graphite, ghstack, git town, Sapling, spr
- Notes Git's --update-refs option for reducing rebases
- States stacking is independent of language and of rebase vs merge
Best for: Developers and teams who work with pull requests and want to understand the stacked workflow and the tools that automate it.
Good for
- Explains the workflow step by step, including how a stack can be structured so one change lands ahead of another
- Covers the rebasing burden that makes manual stacking impractical with the Git CLI alone
- Links out to several tools, including open-source CLIs and a system with built-in stacking
Watch out for
- Provides guidance rather than its own CLI, extension or web interface
- Third-party tools are listed with brief descriptions and external links, not direct comparisons
- No pricing information is given for the site or for the linked tools
Stacking at a glance
- Website
- stacking.dev
- Category
- Development › Git & Code Hosting
- Type
- Website
- Pricing
- Not confirmed. Check the site
- Platforms
- Web
- Open source
- Not stated
- Language
- English
- Last checked
- Oct 5, 2026 · Online when checked
- Listed
- Oct 5, 2026
Stacking alternatives
Tools and sites you could use instead, ranked by how closely they match.
Imgbot compresses image files in GitHub repositories and opens a pull request for review after applying the changes.
Open source
24 alternatives
CatLight sends actionable alerts about software builds, tasks, and pull requests that developers monitor.
SemanticDiff provides language-aware diffs for reviewing GitHub commits and pull requests.
Manage Git workflows through RelaGit, a graphical version control client for developers.
Git workflows on Windows, Mac, and GNU/Linux are managed with Gut, a command-line client.
Popular in Git & Code Hosting
Well-known listings from the same topic.
GitHub CLIcli.github.comCodebergcodeberg.orggit.sr.htgit.sr.htGitstar Rankinggitstar-ranking.comGit LFSgit-lfs.comStar Historystar-history.com
Stacking FAQ
Do I need a special tool to stack?
The site says you can start stacking in almost any repository, and that Git's --update-refs option lets you update a stack with fewer rebases. It notes that parts of the process stay tedious without a tool, such as opening PRs, and lists several tools that automate the workflow.
Can parts of a stack be merged separately?
Yes. The site says that once both PRs are approved they can be landed together or separately, and that a stack can be structured so one change lands ahead of another, for example a new server endpoint landing before code that calls it.
Does stacking require breaking a change into smaller pieces?
The site describes the separation of concerns as a side effect rather than automatic behavior: forcing developers to split a large change into a sequence of smaller dependent changes is what produces that separation.
Is something wrong or out of date?
Tell us and an editor will check it.
Own this website?
Claim this listing
Claim the listing and suggest updates yourself. An editor checks every claim first.