Inside GitHub's Refreshed Repository Pull Requests Page

On September 10, 2026, GitHub launched a public preview of its refreshed repository pull requests page. The update introduces advanced search syntax, a high-density compact presentation mode, and enhanced contextual indicators to help developers triage, review, and manage pull requests more efficiently within individual repositories.

The Evolution of the Repository Pull Requests Page

This release represents a significant modernization of the core repository-level interface where developers spend a substantial portion of their working hours. It builds on a series of platform-wide navigation and dashboard overhauls that GitHub has introduced throughout 2026 to streamline complex developer workflows.

Specifically, this update follows the March 2026 public preview of the refreshed global pull requests dashboard, which brought a unified inbox and saved views to the global github.com/pulls endpoint. While the March update focused on cross-repository aggregation, the September 10 release applies these modern design patterns and query capabilities directly to individual repositories.

Additionally, the refreshed interface integrates with GitHub's native stacked pull requests feature, which entered public preview in July 2026. By bringing stack indicators directly into the repository-level view, GitHub is aligning its interface with modern development practices that rely on small, sequential, and dependent pull requests.

Technical Breakdown of the New Search and UI Features

The refreshed repository pull requests page replaces the classic, rigid filtering bar with a dynamic, query-based search engine and a flexible sidebar layout. The technical changes are divided into three primary categories: search capabilities, layout density, and contextual metadata.

Advanced Search Syntax and Content Assist

The updated page supports complex logical query structures, moving beyond simple key-value filtering. Developers can now write queries using AND and OR logical operators, alongside nested parentheses to group conditions. To assist users in writing these complex queries, GitHub has introduced "Content Assist," an auto-complete utility that suggests valid filters, teams, and organizations dynamically as you type.

For example, a developer can now run a query that targets pull requests authored by themselves or involving them, while filtering out draft PRs or specific labels across a complex repository structure:

(author:@me OR involves:@me) AND is:open AND -label:"do not merge"

This query capability brings the power of GitHub's global search index directly into the repository-level context, reducing the need to jump to external search tools or write custom API scripts to audit open work.

Collapsible Sidebar and Compact Presentation Mode

To maximize screen real estate, the refreshed UI introduces two major layout options:

• Collapsible Sidebar: A persistent panel on the left provides quick-access toggles for standard views such as "Authored by me" and "Involves me." This sidebar can be collapsed to free up horizontal space.
• Compact Presentation Mode: A high-density layout setting designed for maintainers and reviewers on large-scale repositories. This mode reduces row padding and icon sizes, allowing more pull requests to fit on a single screen without scrolling.

Enhanced Context Indicators

Instead of forcing users to click into individual pull requests to check their status, the refreshed list displays real-time metadata indicators directly on each row:

• Status Check Counts: Displays the exact number of passing, failing, or pending CI/CD checks.
• Stack Indicators: Identifies if a pull request is part of a chain of dependent branches, linking directly to the parent or child pull requests in the stack.
• Unread Update Indicators: Visually highlights pull requests that have received new commits, comments, or reviews since the user last viewed them.

Impact on Engineering Workflows

For engineering teams, these changes directly impact daily developer velocity and triage efficiency. In high-volume repositories, finding relevant pull requests has historically been a bottleneck, often requiring developers to maintain bookmark folders of complex search URLs.

The combination of logical operators and the collapsible sidebar simplifies triage. Teams can now quickly isolate pull requests that require immediate attention—such as those with failing status checks or pending reviews—without wading through noise. The integration of stack indicators also makes it easier to track the progress of complex, multi-part feature rollouts, preventing developers from accidentally merging pull requests out of order.

Adoption, Rollback, and Known Limitations

The refreshed repository pull requests page is currently in public preview and is available to all GitHub users. Users can opt into the experience by clicking the Preview badge located at the top of the pull requests page inside any repository.

Because this is a public preview, GitHub has not announced a deprecation date for the classic interface. Developers can roll back to the previous design at any time if they encounter issues. To revert, click the Preview badge at the top of the page and select the Switch back option. Feedback can be submitted directly to GitHub engineers via the Give feedback option under the same menu.

Known Limitations in the Public Preview

Before standardizing team workflows around the new interface, platform engineers and team leads should be aware of several functional gaps in the current preview release:

Teams that rely heavily on milestones for sprint planning or perform frequent bulk triage (such as bulk-closing stale PRs) should continue using the classic interface or leverage the GitHub CLI for those tasks until these gaps are addressed in future preview iterations.