github / github/branch-deploy

Github Environments - Required Reviewer option ?

Abierto
#352 3 comentarios 0 reacciones 0 asignados Ver en GitHub
enhancement question
Lenguaje dominante
TypeScript
Estrellas
576
Forks
74
Merge medio
11 h 7 min
PR fusionados (30 d)
1

Descripción

### 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 :

![{6CF1901D-0F76-4158-8058-0E58C9BF301E}](https://github.com/user-attachments/assets/0bb9ca6e-8d4f-4fed-b8d5-c6b991223856)

But if its enable branch-deploy fails with :

.deploy production

![{5F20E4B4-78B7-472C-A6DA-775A011F01F9}](https://github.com/user-attachments/assets/0b6eb946-de44-4100-a571-a35a491d841f)

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?

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
github, github-actions
Área
authorization, ci-cd, devops
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
20/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.