DEV TOOLS Signal 409
GitHub stacked PR public preview works with Jujutsu via gh-stack extension
↗
A tutorial explains how to use GitHub's stacked pull request feature, released into public preview, with the Jujutsu version control system through the gh-stack CLI extension.
GitHub's stacked PR feature now has documented support for jj, but the workflow is manual: every commit in a stack needs its own bookmark, and inserting commits anywhere but the top requires deleting and recreating the entire stack. Engineers using jj can adopt this today, but should expect friction compared to native git workflows.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
GitHub released its stacked PR feature into public preview on 2026-07-30, with documented support for git-compatible systems like Jujutsu.
The workflow requires the gh-stack CLI extension and a bookmark for every commit in the stack, managed manually via jj bookmark commands.
Adding commits to the middle or bottom of a stack is not supported by gh-stack and requires deleting the stack on GitHub and recreating it from scratch.
THE READ
What the cluster adds up to.
GitHub's stacked PR feature entered public preview on 2026-07-30, primarily targeting git users but with documented support for git-compatible version control systems like Jujutsu (jj). The article is a practical primer for bridging the two, requiring three CLIs, git, jj, and gh, plus the github/gh-stack extension installed via gh extension install github/gh-stack. It was tested against jj v0.43.0, git v2.52.0, gh v2.96.0, and github/gh-stack v0.1.0.
The core workflow hinges on jj bookmarks, which correspond to git branches. GitHub's stacked PRs require every PR to have a bookmark, so users must create one per commit in the stack. The article recommends learning jj's bookmark aliases, jj b l to list, jj b s to set, jj b a to advance, and notes that the default bookmark-advance behavior can be customized by overriding the bookmark-advance-to revset in jj's config.
Creating a stack involves naming each commit with a bookmark, then running gh stack link with a jj revset that selects the stack's commits. The link subcommand uploads bookmarks to GitHub, creates draft PRs, and connects them into a stack. Adding a new commit to the top of the stack is straightforward: create a bookmark, push any modified downstack commits with jj git push, then re-run gh stack link. Existing PRs are skipped and the new branch gets a new draft PR linked into the stack.
A significant limitation is that gh-stack cannot insert commits into the middle or bottom of an existing stack. Attempting to do so produces an error stating new PRs must be added to the top. The workaround is to delete the stack in GitHub's web UI, create a bookmark for the new commit, force-push all rebased commits with jj git push, and re-run gh stack link to recreate the entire stack from scratch. This makes structural changes to a stack expensive in terms of manual effort.
Only one feed carried this story, so there is no corroboration from independent sources on the feature's stability or adoption. The article is part of a series on stacks in Jujutsu and reads as a tutorial rather than a news report. Engineers evaluating this workflow should treat it as an early-stage integration: the tool versions are low (gh-stack is at v0.1.0), the workflows are manual, and the article itself anticipates that future UI tools will automate bookmark creation.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER