required status check
A check, such as a CI job, that must pass on a pull request before branch protection allows it to merge.
In more detail
Branch protection matches required checks by exact job name, so renaming a job, changing a matrix value or skipping the job with a paths filter can leave the pull request waiting forever. A small gate job that needs the others gives branch protection one stable name to watch.
Related terms
- 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.
- gate job — A small job that needs every other important job, so branch protection can require its one stable name.
- event filter — Keys under an event, such as branches, tags and paths, that narrow which pushes or pull requests start a workflow.
- strategy matrix — A job setting that expands one job description into one job for every combination of the listed values.
Taught in
- Triggers and the Event Model — Continuous Integration & Continuous Delivery Pipelines
- Scaling with Matrix Builds — Continuous Integration & Continuous Delivery Pipelines
- Expressions, Contexts And The If That Is Always True — GitHub Actions (GH-200) Exam Prep
- Matrices, Needs And Concurrency: The Shape Of A Run — GitHub Actions (GH-200) Exam Prep
- Why It Ran, Why It Did Not: Reading Runs, Jobs And Checks — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep