Name: GitHub ships native stacked pull requests
Uploaded: 2026-07-31T09:00:00+00:00
Duration: 48 s
Description: GitHub put stacked pull requests into public preview on July 30, 2026, giving every repository a native way to split one large change into an ordered series of small, independently reviewable PRs. Merging one layer automatically rebases and retargets the PRs above it, the exact problem third-party tools like Graphite were built to solve.

GitHub ships native stacked pull requests.

Software · 2026-07-31 · 48s

GitHub put stacked pull requests into public preview on July 30, 2026, giving every repository a native way to split one large change into an ordered series of small, independently reviewable PRs. Merging one layer automatically rebases and retargets the PRs above it, the exact problem third-party tools like Graphite were built to solve.

Read the full story: GitHub Ships Native Stacked Pull Requests in Preview →

Transcript

GitHub just shipped something developers have wanted for years. Stacked pull requests, built right into GitHub, in public preview as of July 30th. Here's the idea. Instead of one giant nine hundred line pull request nobody wants to review, you split it into a chain of small ones, each one targeting the layer below it. That part isn't new. Tools like Graphite and Sapling have done this for a while. What's actually new is the hard part. When you merge one layer in the middle of the stack, GitHub automatically rebases and retargets every PR above it. No more force pushing four branches by hand. You can build a stack from the CLI, the website, mobile, or straight from a coding agent. And that last part matters, because agents are now the ones generating the giant diffs nobody wants to review in one piece.