Feature request: require multiple reviewers in an environment protection rule

[Mahoney]

Select Topic Area

Product Feedback

Body

Hi. We use the "Deployment protection rules" on Environments to gate deployments.

For SOC2 compliance we need to require 2 separate reviewers to get an approval to deploy to live.

GHA currently only supports this with "Prevent self-review: Require a different approver than the user who triggered the workflow run.".

However, our deployment workflows are started automatically by a bot, so this does not work for us.

I propose changing it to a "Required number of reviewers:" field with a checkbox "Consider the user who triggered the workflow run to have approved it".

Our current workaround is to have two jobs, each for a separate environment, each requiring review, and a subsequent action that enforces that they were each reviewed by a different person. But that's very ugly.

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