GitHub redesigns pull request overview page, moves merge status to top in public preview

A summary-first pull request page

GitHub has begun rolling out a redesigned pull request overview page as an opt-in public preview, according to a changelog post published on November 5 that hit the Hacker News front page. The rollout is continuing through the weekend.

The redesign moves merge status and the next available actions to the top of the page in a compact readiness summary. That replaces the current layout, in which the merge box sits below long stretches of comments and timeline events. GitHub frames this as the first step in a broader rethink of the pull request experience: on a large pull request, working out what is blocking progress means scrolling past dozens of comments, and even once developers reach the merge box, they still have to work out what to do next. As review volume grows, that overhead compounds.

A smaller merge box

Rather than simply relocating the merge box, GitHub says it redesigned it. The new version presents the same information in less than half the space and is organised around three things:

• Supporting signals: a compact view of checks, comments and approvals that keeps context nearby without letting every detail compete for attention.
• Unblocking actions: steps such as updating the branch that move the pull request forward.
• Merge readiness: whether requirements have been met, and the ability to merge once they are.

The intended flow is summary first, then detail. From the compact view, developers can jump straight to failing checks, see who still needs to approve, or open the relevant comments.

Catching up and focusing the conversation

The preview also introduces features aimed at helping reviewers find their place and spend less time locating activity:

• Narrow the conversation by filtering for unresolved threads or for comments you wrote, useful for tracking open questions or following up on your own feedback.
• Sort comments from newest to oldest instead of starting with the earliest discussion.
• Use an activity summary in the upper-right corner to find review comments, review requests and other updates.

The header now also hosts actions such as marking a draft ready for review or closing a pull request, with the available options depending on the viewer's permissions.

Opt-in, with an exit

Developers can join the preview through the "Try the Overview page" button in the header. The same menu allows switching back to the classic overview at any point during the preview period.

GitHub says it opened the preview early so users can test the new direction on their own pull requests, and it is collecting feedback and issue reports in a dedicated discussion linked from the changelog post. The company is explicit that this is a starting point rather than the finished pull request experience, and it is asking users what is easier to find, where they still lose context, and what sends them back to the old layout.

Why it matters

The pull request page is core daily infrastructure for millions of developers, and GitHub is proposing a meaningful shift in its information architecture: away from a chronological timeline with merge controls at the bottom, toward a summary-first, action-oriented view at the top. If the direction sticks, it changes how review status is scanned and how blocking issues are triaged on the industry's most widely used code host.

The opt-in rollout and the escape hatch back to the classic overview signal that GitHub expects iteration. But describing this as merely the beginning of a larger rework of pull requests suggests further changes to code browsing, review flow and conversations are likely to follow, and teams that have built habits, or tooling, around the current page layout should watch the preview closely.