Product Update

GitHub Refreshes Pull Request List Page with Advanced Filters

GitHub's refreshed pull request listing page is in public preview. New features include AND/OR search, compact mode, collapsible sidebar, and more PR context.

LUMIEN4 min read
GitHub Refreshes Pull Request List Page with Advanced Filters

GitHub has put its redesigned repository pull request listing page into public preview for all users. The update brings content-assisted filtering, advanced AND/OR search with nested queries, a collapsible sidebar for common filters, and a compact display mode. Several features are still missing, including bulk updates and milestone visibility, so GitHub is treating this as a preview rather than a full rollout.

What happened

Feature Detail
Status Public preview, available to all GitHub users
Search operators AND, OR keywords plus nested searches
Quick filters Collapsible sidebar with “Authored by me” and “Involves me”
Display option Compact presentation mode for higher PR density
Extra context Status check counts, stack indicator, unread update indicators

GitHub’s new pull request listing page replaces the classic view at the repository level, where teams browse and triage open PRs. The redesign focuses on helping developers find the right PR faster without manually scrolling or composing raw search queries from memory.

What’s new in the filtered PR view

Content assist is the headline addition: as you type a filter, GitHub suggests valid options so you don’t need to remember exact syntax. Combined with proper boolean operators (AND, OR) and the ability to nest searches, the new interface should handle complex filtering that previously required workarounds or GitHub’s global search bar.

The collapsible sidebar surfaces shortcuts like “Authored by me” and “Involves me” in one click, which cuts down repetitive typing for common triage workflows. Compact mode is a straightforward density switch: more PRs per screen, less scrolling. The additional context columns, status check counts, a stack indicator for stacked PRs, and unread update flags, give reviewers a faster read on PR health before opening anything.

What’s still missing

GitHub is transparent about the gaps. Four things are not yet available in the preview:

  • Milestones are not shown on the listing page.
  • Bulk updates (closing or labeling multiple PRs at once) are not supported.
  • Emojis in labels do not always render correctly.
  • Custom views cannot be saved for later use.

Teams that rely heavily on milestones or bulk triage actions will likely want to hold off or keep the classic view open in a second tab while the preview matures. To revert, click the Preview badge at the top of the page and choose “Switch back.”

Why it matters

For teams with large repositories and many contributors, the PR list is where review bottlenecks form. A filter that takes three steps to configure is a filter that doesn’t get used. Content assist and saved views (once they arrive) are the kind of quality-of-life details that compound over hundreds of daily interactions. The compact mode also matters for reviewers who track multiple repos: less scrolling means faster triage.

For agencies and developers managing client codebases, a better PR interface means less time navigating and more time shipping. If your team uses web development workflows with regular code review cycles, this change is worth testing now while GitHub is still collecting feedback.

Our take

The feature set is sensible, not flashy. AND/OR search and content assist are table-stakes improvements that most developer tools shipped years ago, so GitHub is catching up more than innovating here. That said, the compact mode and stack indicator show genuine awareness of how modern teams actually work, particularly those using stacked PRs to break large features into reviewable chunks.

The public preview framing is honest. The missing bulk-update capability is a real limitation for anyone doing repository housekeeping. We’d recommend testing the new page for daily review work, but keep the classic view available for bulk triage until that gap closes.

This follows a broader pattern of GitHub iterating on its core UI. We covered a related update in the GitHub Copilot for JetBrains enterprise sandbox update, where GitHub added controls for coding agent workflows. The PR page redesign is a different layer, but it signals the same direction: making the repository interface faster and more actionable for professional teams.

What to do about it

  1. Open any repository on GitHub and look for the Preview badge at the top of the pull requests page to opt in.
  2. Test the AND/OR search operators with filters your team uses daily to check whether they behave as expected.
  3. Enable compact mode if you review PRs across multiple repositories and want higher information density.
  4. Submit feedback via the Preview badge’s “Give feedback” option before the preview closes, GitHub states your input shapes the final release.
  5. Switch back to the classic view for any workflows that require milestones or bulk updates until those features are added.

Try the new view on your busiest repository first: that’s where the filtering improvements will show the clearest benefit.

Source: GitHub Changelog

Frequently asked questions

How do I try the new GitHub pull request page?

Open any repository on GitHub, go to the Pull Requests tab, and look for the Preview badge at the top of the page. Click it to opt in to the new experience.

Can I switch back to the old GitHub pull requests view?

Yes. Click the Preview badge at the top of the pull requests page and select 'Switch back' to return to the classic experience at any time.

What filters are available in the new GitHub PR listing page?

The new page includes content assist for filter discovery, AND/OR keyword search with nested queries, and a collapsible sidebar with quick filters like 'Authored by me' and 'Involves me'.

What is missing from the new GitHub pull request page?

As of public preview, milestones are not shown, bulk updates are not available, label emojis sometimes fail to render, and custom views cannot be saved.

More from Web Development