environment protection rule
A rule on a deployment environment, such as required reviewers, a wait timer or allowed branches, checked before a job may deploy there.
In more detail
The rule is configured in GitHub rather than in the YAML file, so policy can change without editing release logic. A job waiting on it is pending, not failed.
Related terms
- deployment environment — A named target such as staging or production that a job declares, so GitHub can attach its own variables, secrets and protection rules.
- manual approval — A deliberate pause in which a named reviewer must approve before a deployment job continues.
- branch protection rule — A setting on a hosting service that stops changes reaching a branch, usually main, unless conditions such as an approved review and passing checks are met.
Taught in
- Defining Environments in GitHub Actions — Continuous Integration & Continuous Delivery Pipelines
- Environment Protection and Manual Approvals — Continuous Integration & Continuous Delivery Pipelines
- The Workflow That Ran On A Stranger's Pull Request — GitHub Actions (GH-200) Exam Prep
- Reusable Workflows: Inputs, Secrets And Outputs Across A Call — GitHub Actions (GH-200) Exam Prep
- Secrets And Variables By Scope: Precedence, Access And The REST API — GitHub Actions (GH-200) Exam Prep
- Environments: Reviewers, Wait Timers And Deployment Rules — GitHub Actions (GH-200) Exam Prep