GitHub pull request Overview page: merge status at the top

GitHub just moved the merge box to the top of the pull request. The new pull request Overview page, in opt-in public preview since November 5, shows what's blocking a PR and what to do next before you scroll a single comment. Small change. But when agents open more pull requests than humans can read, the time spent finding the merge box is the time you're not reviewing code.

What actually happened

GitHub announced the Overview page in its changelog, with rollout continuing through the weekend. What's in the preview:

• A redesigned merge box at the top. Merge status, checks, comments and approvals in what GitHub says is less than half the old space, plus actions like updating your branch or merging when requirements pass.
• Conversation filters. Show only unresolved conversations, or only comments you wrote.
• Newest-first sorting. Read the latest comments first instead of starting at the opening discussion.
• An activity summary in the upper-right that points to review comments, review requests and other updates.
• Header actions to mark a draft ready for review or close the PR, depending on your permissions.

To turn it on, click Try the Overview page in the PR header. The same menu takes you back to the classic view. GitHub calls this "a starting point, not the finished pull request experience," so expect it to change.

Why the pull request Overview page matters for your business

Code review is now the slow step. Coding agents write a branch in minutes. A human still has to decide if it ships. We wrote about this when stacked pull requests went GA and when Octoverse showed how many PRs agents now start. A page that answers "what's blocking this?" in one glance is a real fix for that bottleneck.

It only helps if your repo gives it real signals to show. Before you try it:

1. Make checks required. A readiness summary is only as honest as your branch protection. If tests aren't required, "ready to merge" means nothing.
2. Use "unresolved" as your merge gate. Filter for open conversations before you approve an agent's PR. If the agent "fixed" a comment, confirm the thread is actually resolved.
3. Keep PRs small. A compact merge box doesn't make a 3,000-line agent diff reviewable.

It's free, it's opt-in, and you can switch back. Turn it on for the reviewer who handles the most agent PRs and ask them in a week if it saved time.

Sources: GitHub Changelog: New pull request overview page in public preview.