GitHub has opened a public preview of a new Overview page for pull requests, announced in its changelog on November 5, 2026. The page is opt-in, and the rollout keeps going through the weekend, so some accounts may not see the option right away.
The change targets a daily annoyance for reviewers. On a busy pull request, the merge box sits at the bottom of a long timeline, and finding out what blocks a merge can take a lot of scrolling. The new page pulls that status to the top and adds tools to filter and reorder the discussion.
What GitHub Changed
The first piece GitHub reworked is the merge box, the panel that tells you if a change is ready to go in. In the preview it no longer waits at the end of the conversation.
Instead, it appears near the top as a short readiness summary. GitHub says the redesign fits the same details into less than half of the old space.
The summary has three jobs:
- Supporting signals: a condensed view of checks, comments and approvals, so the context stays close without crowding the page.
- Blockers: actions that help the pull request progress, such as bringing your branch up to date.
- Merge readiness: a clear signal of whether requirements are met, with the merge action available once they are.
From the summary you can jump to the detail behind it. For example, you can go straight to a failing check, see which reviewers still have to approve, or open the comments that matter for your next step.
New Ways to Follow the Conversation
The preview also adds controls for long discussions. You can filter the conversation to show only unresolved threads, or only comments you wrote yourself. That makes it easier to see open questions or to check whether others answered your feedback.
Comments can now be sorted with the latest first, instead of always starting from the first message. A summary in the upper-right corner points to new review comments, pending review requests and similar recent activity, which helps when you return to a pull request after a day away.
The page header gains a few actions as well. Depending on your permissions, you can mark a draft as ready for review or close the pull request from the header, without scrolling to the bottom.
How to Try the Overview Page
To opt in, open a pull request and use the opt-in button at the top of the page. The same menu lets you switch back to the classic overview at any time during the preview, so there is little risk in testing it.
GitHub describes this release as an early starting point rather than the final design of the pull request experience. It is collecting feedback and bug reports in a community discussion linked from the changelog, and it asks users what is easier to find, where they still lose context, and what sends them back to the classic view.
What It Means for Developers
For reviewers who handle many pull requests a day, the main gain is speed. Seeing checks, approvals and blockers in one compact block at the top should cut the time spent hunting for the reason a merge button is grey.
The unresolved filter is also useful just before merging, as a quick way to confirm no review thread was left open.
Authors benefit too. Filtering by your own comments, and reading the newest messages first, helps you catch up on replies after a long review cycle. Teams with strict branch protection rules, many required checks or several code owners will likely notice the difference most.
Because the preview is opt-in and reversible, a practical approach is to try it on your next few reviews and keep the classic view as a fallback.
If your team writes internal guides with screenshots of the pull request page, wait before updating them, since GitHub says the layout will keep changing. Browser extensions or scripts that read the pull request page may also need checking once the new view becomes the default.
This update fits a wider pattern of GitHub reworking how code review works as more changes, including those from AI coding agents, land in pull requests. We covered related moves recently, such as GitHub Agentic Workflows reaching general availability and workflow lockfiles for GitHub Actions.
Conclusion
GitHub's new pull request Overview page moves merge status and next steps to the top, shrinks the merge box, and adds filtering and sorting for long conversations.
It is available now as an opt-in public preview, with a one-click way back to the classic layout. Developers who review often should try it and share feedback while GitHub is still shaping the design.
Sources
See my articles more often when you search Google.
