Deploying Code to Azure via GitHub Actions
Overview
We use GitHub Actions as our CI/CD pipeline to deploy code from GitHub to Azure. The pipeline is fully automated and tied to branch activity.
Branch-to-Environment Mapping
-
develop→ Staging -
master→ Production
CI/CD Flow
-
Continuous Integration (CI): When changes are pushed or merged to either branch, GitHub Actions runs the pipeline (e.g., build/validate steps).
-
Continuous Delivery/Deployment (CD):
-
Push/merge to
develop→ automatic deployment to Staging. -
Push/merge to
master→ automatic deployment to Production.
-
How to Use
-
Work on a feature branch.
-
Merge into
developto deploy to Staging for validation. -
Merge into
masterto deploy to Production.
Notes
-
No manual steps are required once changes reach the target branch—the CI/CD workflow triggers and completes deployment automatically.