workflow (GitHub Actions)
A YAML file in the .github/workflows folder of a repository that names its triggers and the jobs to run.
In more detail
A workflow has a name, an on key listing the events that start it and a jobs key. Because it lives in the repository, a change to the pipeline is a commit that can be reviewed and reverted like any other code.
Examples
name: pipeline
on:
push:
branches: [main]
jobs:
release:
runs-on: ubuntu-latest
steps:
- run: bash tests/run.shbun run ci/validate-workflow.ts ci/pipeline.ymlIn this course: putting the gate's required checks in a workflow file keeps the policy visible, versioned and reviewable with the code.Related terms
- GitHub Actions — GitHub's built-in automation service that runs workflows, written as YAML files in a repository, on runners when events happen.
- job (GitHub Actions) — A named group of steps in a workflow that runs on one runner of its own.
- on — The top-level workflow key that lists which events start the workflow, with optional filters for each.
- YAML — A human-friendly text format for configuration, where indentation shows structure.
- runner — A machine running the runner application that picks up a queued job, runs its steps and reports the result.
- pipeline — An automated sequence of steps, such as build, test, scan and publish, that runs on every change.
- quality gate — A check, or set of checks, that a change must pass before it can move on, such as being merged or promoted to the next pipeline stage.
Taught in
- What Is a Pipeline? — Continuous Integration & Continuous Delivery Pipelines
- Workflows, Jobs, Steps, and Actions — Continuous Integration & Continuous Delivery Pipelines
- Triggers and the Event Model — Continuous Integration & Continuous Delivery Pipelines
- Continuous Integration — DevOps & Site Reliability Engineering
- The Workflow That Ran On A Stranger's Pull Request — GitHub Actions (GH-200) Exam Prep
- How GH-200 Asks: Pacing, Weights And Stems — GitHub Actions (GH-200) Exam Prep
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Matrices, Needs And Concurrency: The Shape Of A Run — GitHub Actions (GH-200) Exam Prep
- Reusable Workflows: Inputs, Secrets And Outputs Across A Call — GitHub Actions (GH-200) Exam Prep
- Outputs, Artifacts, Caches And Job Summaries — GitHub Actions (GH-200) Exam Prep
- Why It Ran, Why It Did Not: Reading Runs, Jobs And Checks — GitHub Actions (GH-200) Exam Prep
- Failed Runs: Debug Logging And Re-Running The Right Jobs — GitHub Actions (GH-200) Exam Prep
- Workflow Templates: Sharing Workflows Across An Organization — GitHub Actions (GH-200) Exam Prep
- action.yml: Inputs, Outputs, Runs And Branding — GitHub Actions (GH-200) Exam Prep
- Governing Actions: Allow Lists, SHA Pinning And Rulesets — GitHub Actions (GH-200) Exam Prep
- Self-Hosted Runners At Scale: Labels, Groups And ARC — GitHub Actions (GH-200) Exam Prep
- GITHUB_TOKEN: Least Privilege, Job By Job — GitHub Actions (GH-200) Exam Prep
- Environments: Reviewers, Wait Timers And Deployment Rules — GitHub Actions (GH-200) Exam Prep
- Script Injection: When An Issue Title Becomes Code — GitHub Actions (GH-200) Exam Prep
- Supply Chain: Pinning, Trusted Actions And Attestations — GitHub Actions (GH-200) Exam Prep
- YAML-Reading Sprint: What Happens When This Runs? — GitHub Actions (GH-200) Exam Prep
- What To Automate Away — Automated Testing, TDD & Quality Engineering