Decouple requesting a review from requiring an approval

[IvanRibakov]

🏷️ Discussion Type

Product Feedback

Body

Feature

Required reviewer rule

Problem statement

While the feature claims to focus strictly on policy enforcement, it automatically requests reviews from the required teams as soon as a PR is opened. Because all required teams are pinged simultaneously at the very beginning, it is impossible to natively implement N-stage (sequential) PR reviews.

Desired change

Modify the feature to allow strict policy enforcement (requiring the approval to merge) without automatically requesting a review from the required teams when the PR is first opened.

Known workaround

Use workflow actions to validate presence of approvals from members of certain teams and then make those checks required. This however has the downside of validation/enforcement not being protected by platform's RBAC, so in some extreme cases malicious actor can bypass required reviews.

[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. ⭐