Concepts for GitHub Actionss
GitHub Actions concepts are the building blocks of a pipeline. A workflow is a YAML file triggered by events. It contains jobs that run on a runner, and each job has steps that either run a shell command or use a prebuilt action. This structure is how building and testing code is automated.
Stage: Workflow Basics · Part of the GitHub Actions roadmap · Last reviewed 19 November 2026
What to learn in Concepts
- Write a workflow file with an on trigger, a job and steps
- Use actions/checkout and a setup action to prepare a language runtime
- Run a build and test commands and read the job log
- Define job dependencies using the needs keyword
- Run a test matrix across several versions or operating systems
Concepts interview questions
What is the difference between a job and a step?
A job is a set of steps that run on one runner, and jobs run in parallel by default unless linked with needs. A step is a single task inside a job, either a shell command or an action, and steps share the runner's filesystem.
What does a matrix strategy do?
A matrix generates multiple job runs from combinations of variables, such as Node versions and operating systems. It lets you test a project across environments from one job definition, and you can exclude combinations or stop on first failure.
Where Concepts fits in the GitHub Actions roadmap
Concepts belongs to the Workflow Basics stage (beginner level), which takes about 12 hours. Your first automation.
Other units in this stage
Back to the full GitHub Actions roadmap