Azure / Azure/static-web-apps

production_branch option does not work with pull_request trigger in GitHub Action

未关闭
#1,663 0 条评论 4 个 reaction 已指派 1 人 已被 @LongOddCode 认领 在 GitHub 查看
bug
主要语言
没有语言数据
星标
346
派生
67
PR 合并指标
30 天内没有已合并 PR

描述

**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.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。