How to filter Non-Mandatory Reviewers in Pull Requests

[wassim-ben-amor]

Select Topic Area

Question

Body

Hello,
I’m facing a challenge with how reviewers are displayed in pull requests, and I’m wondering if there’s a way to make things clearer.
Here’s an example of my CODEOWNERS setup:

apps/app1 @team1  
apps/app2 @team2  
apps/app3 @team3  
/package.json @devxteam  

If a PR modifies:

• All package.json files across the apps (apps/app1/package.json, apps/app2/package.json, apps/app3/package.json)
• app1/index.ts

GitHub lists all related teams (@team1, @team2, @team3, and @devxteam) as mandatory reviewers.
However, branch protection rules require:

1. Only one approval from @devxteam for the package.json changes (which is often handled by the DevX team managing dependencies).
2. Approval from @team1 for the index.ts change.

In this setup, it's difficult to determine if approvals from @team2 or @team3 are truly required. This becomes particularly challenging in a monorepo with 100+ apps, where identifying which approvals are still blocking the merge can be confusing and time-consuming.

Why This Matters
This is especially relevant for DevX teams maintaining shared dependencies (like package.json files). They don’t always need individual app teams’ approvals to merge, but the current GitHub UI makes it appear as though their approval is required.

Additionally, our teams merge pull requests via the queue, which only allows merging when the "Merge" button turns green. With unclear UI feedback about which approvals are still required, we cannot determine when the PR is ready to be queued for merging. This slows down the process significantly.

My Question
Is there a way to:

1. Keep all the CODEOWNERS listed as reviewers, but provide UI feedback that clearly indicates which teams’ approvals are still blocking the merge?
2. Filter mandatory reviewers in the UI so that it’s obvious which approvals are required to meet branch protection rules (e.g., @devxteam for package.json changes and @team1 for index.ts)?

Any advice or solutions would be greatly appreciated!
Thank you!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬