GitHub PR Search Bug: Multiple <code>-involves:</code> Filters Fail, Impacting Software Development Metrics

A recent update to GitHub's repository Pull Requests page has introduced a significant regression for developers who rely on advanced search filters to manage their review queues. Community member pbsds initiated a discussion highlighting that the ability to use multiple -involves: qualifiers in PR searches no longer functions as expected, leading to unfiltered results and a noticeable dip in workflow efficiency.

The Bug: Multiple -involves: Filters Silently Fail

The core of the issue lies in the refreshed repository Pull Requests page, which became generally available on September 21, 2026. Previously, developers could stack multiple -involves:username filters to exclude several users or bots from their PR review lists. This was a common practice for streamlining review processes, allowing teams to focus on relevant contributions without distraction from automated processes or highly active individuals whose PRs might not require immediate attention from a specific reviewer.

However, with the update, applying a second -involves: term in a search query causes the entire involves filter to be silently dropped. The search then returns the complete, unfiltered list of pull requests, effectively negating the user's intent. This behavior was meticulously reproduced and confirmed by Sagargupta16, who provided clear numerical evidence using the NixOS/nixpkgs repository. For example, while -involves:r-ryantm correctly narrowed results, adding a second filter like -involves:r-ryantm -involves:Mic92 yielded the same count as an entirely unfiltered query.

This regression directly impacts developer productivity and the ability to accurately track and manage contributions, potentially skewing insights derived from a software development metrics dashboard. Efficient filtering is crucial for maintaining a clean and focused review pipeline, which in turn contributes to faster merge times and overall project velocity.

Where the Bug Does NOT Occur

It's important to note that this issue is specific to the new repository Pull Requests page. The same search query strings continue to function correctly in other GitHub interfaces:

• The global search page (/search?type=pullrequests&q=...)
• The GitHub Search API
• The GitHub CLI (gh search prs)

This distinction strongly suggests a parser edge case or a bug specific to the front-end implementation of the refreshed PR page, rather than a change in GitHub's underlying search syntax.

Effective Workarounds for Developers

Until GitHub addresses this regression, the community has identified several practical workarounds to restore the desired filtering capabilities:

1. Expand -involves: into its constituent qualifiers: The involves: qualifier is documented as a logical OR of author, assignee, mentions, and commenter. You can manually expand your query to exclude multiple users across these categories. For example, instead of -involves:r-ryantm -involves:Mic92, use:

   is:pr is:open -author:r-ryantm -assignee:r-ryantm -mentions:r-ryantm -commenter:r-ryantm -author:Mic92 -assignee:Mic92 -mentions:Mic92 -commenter:Mic92

   This expanded form is honored on the new PR page and can be saved as a custom filter for convenience.

2. Utilize the global search page or GitHub CLI: Since the bug is localized to the repository PR page, simply performing your multi--involves: search on the global search page or via the CLI will yield correct results.

   gh search prs --repo NixOS/nixpkgs --state open -- -involves:r-ryantm -involves:Mic92

3. Employ boolean syntax with NOT and OR: As suggested by kurupdevs, explicitly stating the boolean logic can bypass the parsing issue. Instead of repeating -involves:, structure your query to negate a group of involved users:

   NOT (involves:r-ryantm OR involves:Mic92)

The swift identification and confirmation of this bug by the GitHub community underscore the importance of robust search functionality for developer workflow. While these workarounds offer temporary relief, a permanent fix from GitHub will be crucial for maintaining seamless productivity and accurate software development metrics dashboard reporting on the platform.