Azure / Azure/static-web-apps

production_branch option does not work with pull_request trigger in GitHub Action

Abierto
#1,663 0 comentarios 4 reacciones 1 asignado Reclamado por @LongOddCode Ver en GitHub
bug
Lenguaje dominante
Sin datos de lenguaje
Estrellas
346
Forks
67
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**Describe the bug**

I have an Angular application with 4 environments Dev, UAT, Staging and Production.
The process we want to follow for new feature addition is as follows:
1. Create a new feature branch from the main branch.
2. Build the feature and create a pull request.
3. Pull request will trigger the deployment in an Azure static app specific for Development.
4. After successful deployment in development App, workflow will wait for the approval for UAT, Staging deployment, which again will deploy the new feature in the UAT, staging Apps.
5. After verification in UAT and Staging the branch will be merged into main and deployed to Production Azure static app.

Now problem here is, I am not able to deploy to the production environment of an Azure static app on pull_request trigger even after using production_branch option. Although I can deploy to production environment from a specific branch on a push trigger.
So I was wondering, if it's possible to use the production_branch option with pull_request trigger in GitHub Action.

**To Reproduce**
Steps to reproduce the behavior:
1. Try to deploy to the production environment of an Azure static app on pull_request trigger of GitHub Action.

**Expected behavior**
I should be able to deploy to production environment of an app from a specific branch on pull request trigger as well, as it's possible on the push trigger.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Device info (if applicable):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.