- Published on
Deployment Status in GitHub Actions
- Authors
- Name
- Bowen Y
active
deployment for each environment
There is only one This can be annoying when I have multiple branches deployed to the same environment and have several open PRs to be merged at the same time. Only the PR that has the active
deployment mark can be merged when I set deployment before merge
branch protection rule.
Solution 1: Run each deployment CICD again when you are reviewing the PR, so that branch's deployment will be the latest one and becomd active
. Then it is good to be merged.
Solution 2: Use dynamic environments. When you use an environment name in your GitHub Actions workflow, GitHub will automatically create that environment if it doesn't already exist. However, we have populated the secrets and variables manually. (TODO: Have to find a total automatic method.)