
At GitHub Universe in October, I talked about multi-model solutions like Copilot Fusion will start dominating benchmarks going forward. But the pace of progress has been faster - ~10% better quality at half cost just few weeks later.

Product @github leading Stacked PRs 🥞 Previously @rockerbox, @eventable Proud @UCBerkeley dropout

At GitHub Universe in October, I talked about multi-model solutions like Copilot Fusion will start dominating benchmarks going forward. But the pace of progress has been faster - ~10% better quality at half cost just few weeks later.

Through internal testing, GitHub’s new Git storage architecture supported 5,000 concurrent agents working on a repo, sending 7,200 pushes per second, all while serving read traffic with consistently low latency.


PRs are changing and so should the UI and how we interact 👀 Try out the preview and let us know what you think!
Confession: I’ve scrolled past dozens of comments on a PR just to find out why I couldn’t merge it. More times than I’d like to admit. Agents have made this a lot worse. They push commits and leave review comments of their own, and all of it lands in the timeline. PR timelines have gotten dramatically noisier, and the few things you actually need to know get buried. My team is rethinking the foundations of the PR experience around that problem, and today the first piece went into public preview. The new Overview page puts merge readiness and your next step right at the top. A summary catches you up on review activity, and you can filter the conversation down to unresolved threads. It’s opt-in and rolling out through the weekend. This is a much-needed start, and there’s a lot more coming as we modernize PRs for the way software gets built now. If you try it, we’d love to hear what still sends you back to the classic view. github.blog/changelog/2026-1…


What an incredible time at #GitHubUniverse! We announced the GA release of Stacked PRs, which included auto-merge support, VS @code integration, and a new stack view in the UI 🥞 Recording of the session and demo 👇 youtu.be/6bv4VZUM2kg?si=bAsM…


Agents don’t just help build features. They can help try to break them, too. In our latest GitHub Podcast episode, Sameen Karim takes us behind the scenes on building stacked PRs. Listen to it wherever you get your podcasts or at youtu.be/sbHoDdAalMI?si=purN…

One of the key design decisions we made with stacked PRs was reusing the existing PR model. It definitely came with some drawbacks, but it’s what made it possible to ship the feature without needing to rewrite all of the core plumbing (and we still had to update a lot!) More on how we built stacks on the latest episode of the @github podcast: youtu.be/sbHoDdAalMI

stacked prs @github behind the scenes. the merge box is way more complex than you think, we touched code that hadn't been updated in a decade, and we set a swarm of agents loose trying to break it 🤯 full episode: youtu.be/sbHoDdAalMI

More on the latest set of updates to stacks here 👇 github.blog/changelog/2026-1…

Note: we will still dismiss approvals for conflicts or mid-stack changes, because that would result in changes that are no longer tree-same

We simulate merging the previously approved head with the new stack merge-base, then compare that result's git tree with the rebased head's tree. If they match and the review's recorded merge-base is still valid, we promote the approval to new head commit

To solve this, we now record the merge-base SHA of the entire stack alongside each review. This is the common ancestor of the reviewed head and the stack's base branch, giving us a reference point for checking the whole stack up to that PR

The challenge was telling the difference between replaying the same reviewed changes on a new base vs. actual changes that have been introduced that need another review. In a stack, that means accounting for the PRs below, too

PR approvals are tied to commit IDs and since a rebase/force-push rewrites those, it would previously always result in reviews being dismissed. We do have a system for "promoting" approvals but historically it only worked with merge commits

Approvals are now retained for Stacked PRs after stack rebases ✅ Whether you use the "Rebase stack" button or partially merge a stack, as long as the diff doesn't change, PR approvals will be kept even if you have "dismiss stale approvals" turned on