Environment "Required reviewers" option not appearing despite GitHub Team plan

[laxmank03]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hi everyone,

Our organization is on the GitHub Team plan (confirmed via Settings > Billing, 9 licenses, $36/month), and we're trying to set up deployment protection rules (Required reviewers) on an environment in a private repository.

What we expected: on the environment's configuration page (Settings > Environments > [environment name]), a "Required reviewers" section where we could add approvers before a deployment job runs, as described here: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment

What's actually happening: this section simply does not appear on the page at all. We only see "Deployment branches and tags" and "Environment secrets", with nothing for required reviewers in between.

What we've already checked:

• Confirmed org billing is genuinely Team, not Free
• Confirmed the repo is Private
• Hard refreshed / tried incognito in case of caching
• Created a brand new test environment from scratch to rule out it being specific to one environment. Same result on the new one too.

We've also opened a support ticket (#4589392) three days ago with no response yet, so posting here in case anyone has run into the same thing or has a workaround.

Has anyone else experienced this? Any insight into what might be causing it would be really helpful.

Thanks!

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

[ECD5A]

This is expected for a private repository on GitHub Team, although the distinction is easy to miss in the environment UI and documentation.

GitHub Team gives private repositories access to environments, environment secrets, variables, and deployment branch/tag restrictions. However, GitHub's current availability note says that required reviewers and wait timers on GitHub Free, Pro, and Team are limited to public repositories. Deployment protection rules such as required reviewers in private or internal repositories require GitHub Enterprise.

That explains the exact UI you are seeing: Deployment branches and tags and Environment secrets are available, while the Required reviewers section is omitted. It is not caused by caching, the environment configuration, or the number of Team seats.

The relevant availability notes are here:

• Deployments and environments — Required reviewers
• Reviewing deployments — Who can use this feature?

So the native options are either to use the rule in a public repository or move the organization to GitHub Enterprise Cloud for a private repository. Also, “required pull request reviewers,” which Team supports in private repositories, is a different feature from environment/deployment required reviewers.