[Feature Request] Support AND Logic in CODEOWNERS for Required Approvals

[AlexJSully]

Select Topic Area

Product Feedback

Body

Currently, GitHub’s CODEOWNERS file only supports OR logic for required reviewers. For example, specifying:

/path/to/files/ @owner1 @owner2

means that a pull request affecting these files requires approval from either @owner1 or @owner2. Firstly, am I misunderstanding this? If not ↓

Feature Request:
I would like to request support for an AND logic in CODEOWNERS, so that it is possible to require approvals from multiple specific owners for a given path.

Proposed Syntax Examples:

• /path/to/files/ (@owner1 @owner2)

→ Requires approval from both @owner1 and @owner2.

• /path/to/files/ (@owner1 @owner2) @owner3

→ Requires approval from both @owner1 and @owner2, or approval from @owner3.

This would allow for more flexible and secure code review workflows, ensuring that files can only be merged when all designated owners have approved.

Summary Table:

CODEOWNERS Entry	Current Behavior	Desired Behavior
/path/to/files/ @owner1 @owner2	@owner1 or @owner2	@owner1 or @owner2 (unchanged)
/path/to/files/ (@owner1 @owner2)	N/A (not supported)	@owner1 and @owner2
/path/to/files/ (@owner1 @owner2) @owner3	N/A (not supported)	(@owner1 and @owner2) or @owner3

Thoughts?

[David-Nash-0]

This is very much needed.

[stephenmwright]

This would be very helpful to our workflow. Good request, very well-written.

[RWhite2025]

This is needed

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[mporadek]

This would be very much appreciated feature.