[Bug]: No way to exclude stages for an environments in GitHub Action Workflows
@taoyangcloud is already working on this.
Since May 5, 2026.
Assessment
This issue has not been assessed yet.
Description
Affected Area
GitHub Actions Workflows
Description
Unlike Azure DevOps, there is no way to select which stages to run on GitHub Action workflows.
It is important that we have the ability to do so in order to avoid execution failures of some workflows when the depenency workflows have not been executed on this stage (i.e. policy assignment workflow will fail on the build stage for prod stages if any policy definitions and initiatives are not deployed in prod environment)
Steps to Reproduce
- Create a new policy definition in a feature branch
- Add the new policy to an existing initiative in the same feature branch
- run the policy defintion workflow from the feature branch
- run the policy initiative workflow from the feature branch
- run the policy assignment workflow from the feature branch
Expected Behavior
Policy assignment workflow will fail
Actual Behavior
Need to have the ability to exclude policy assignment prod build stage
Bicep CLI Version
No response
PowerShell Version
No response
CI/CD Platform
GitHub Actions
Additional Context
No response
- Dominant language
- PowerShell
- Stars
- 22
- Forks
- 5
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/AzPolicyFactory
-
enhancement wontfix
Difficulty 5/5 Over a week Newbie friendliness 35/100
Azure/AzPolicyFactory#41 · 1 comment ·