Instead of pushing one giant PR, you can split a change into smaller dependent layers that are easier to review and merge. GitHub adds stack maps in the PR UI, applies rules and CI against the final target branch, supports bottom-up merging, and ships the gh stack CLI to handle branch creation, rebasing, syncing, and submission.
That means less PR sprawl, better review context, and much less manual pain around dependent branches.
Replies
Flowtica Scribe
Hi everyone!
GitHub now supports Stacked PRs natively.
Instead of pushing one giant PR, you can split a change into smaller dependent layers that are easier to review and merge. GitHub adds stack maps in the PR UI, applies rules and CI against the final target branch, supports bottom-up merging, and ships the gh stack CLI to handle branch creation, rebasing, syncing, and submission.
That means less PR sprawl, better review context, and much less manual pain around dependent branches.
showmd
but why is this only working in combination with `gh`?
Flowtica Scribe
@jollife It’s not only for gh, the stack itself is just standard git branch relationships.
gh stack is GitHub’s way of making the local workflow manageable. The native support is really in the PR UI, plus the merge and CI behavior on GitHub.