Allow Environment Protection Rules to Recognize Organization-Level Team Access through Role assignments

[CrystalDesignDR]

Select Topic Area

Product Feedback

Body

Currently, environment protection rules require teams listed as required reviewers to have direct access to the repository. This means that even if a team has access to the repository through an organization-level role assignment, it is not recognized for environment protection rules unless explicitly added to the repository.

This creates an inconsistent experience compared to other GitHub features like repository rulesets and branch protection rules, which can leverage organization-level access without mandating direct repository access for teams.

Use Case:

• Our organization manages access at the org level, assigning teams to roles that grant repository access across multiple projects.
• We rely on environment protection rules to enforce deployment approvals, but the current requirement forces us to manually add teams to each repository, duplicating effort and increasing the risk of misconfiguration.

Requested Change:

• Update environment protection rules to recognize teams with organization-level access as valid required reviewers, without requiring direct repository access.

This change would simplify workflows for organizations using centralized access management

Daniel

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