event filter
Keys under an event, such as branches, tags and paths, that narrow which pushes or pull requests start a workflow.
In more detail
Each filter has an ignore twin that inverts it. A paths filter is a cheap speed-up because the fastest job is the one that never starts, but it has a trap: if a required check is skipped by a paths filter, it never reports and the pull request cannot merge.
Example
paths:
- 'app/**'
- 'tests/**'Related terms
- on — The top-level workflow key that lists which events start the workflow, with optional filters for each.
- required status check — A check, such as a CI job, that must pass on a pull request before branch protection allows it to merge.
- glob pattern — A pattern that matches names using * for any run of characters, a question mark for one character and [abc] for one of a set.
Taught in
- Triggers and the Event Model — Continuous Integration & Continuous Delivery Pipelines
- The Workflow That Ran On A Stranger's Pull Request — GitHub Actions (GH-200) Exam Prep
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Why It Ran, Why It Did Not: Reading Runs, Jobs And Checks — GitHub Actions (GH-200) Exam Prep
- Faster And Cheaper: Where The Minutes Go — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep