Github Environments - Required Reviewer option ?

### Details

Hello,
Is it possible to apply "Approval Gate" when deploying to PRODUCTION environment ?

Here is an example of existing 'production' which require reviewers on Github Level :


But if its enable branch-deploy fails with :

.deploy production


How can I ensure that deployment to 'production' is managed ONLY by dedicated user(s), and deployment to 'stage' is managed by other repo 'write' users?

Start by reviewing the branch-deploy deployment flow and GitHub Environments' required-reviewer behavior. Reproduce the `.deploy production` case described in the issue, then determine whether the project can enforce dedicated reviewers for production while allowing other repository write users to deploy to stage. Done should include a documented or implemented, verified access-control path.

Written by the indexing model from the issue text.