GitHub Actions Architecture Components
You'll learn: The five core building blocks that power GitHub Actions workflows—and how they fit together to automate your development tasks.
Understanding the Architecture
Think of GitHub Actions like a factory assembly line. Each component has a specific role, and they work together to transform your code from commit to deployment.
The Five Core Components
1. Workflows
The blueprint for your automation. A workflow is a YAML file (.github/workflows/) that defines when and what happens. It's triggered by events like pushes, pull requests, or schedules.
2. Jobs
Independent units of work within a workflow. Each job runs in its own fresh environment and can execute in parallel or sequentially. Jobs are where you group related tasks together.
3. Steps
Individual tasks within a job that run sequentially. A step might check out code, run a script, or call an action. Steps share the same runner environment and can pass data between each other.
4. Actions
Reusable units of code—the "power tools" of GitHub Actions. Actions are pre-built commands (yours or community-contributed) that perform common tasks like deploying to cloud platforms or sending notifications. They eliminate repetitive scripting.
5. Runners
The execution environment (virtual machines) where your jobs actually run. GitHub provides hosted runners (Ubuntu, Windows, macOS), or you can use self-hosted runners for custom requirements.
How They Connect
A workflow contains one or more jobs. Each job runs on a runner and contains multiple steps. Steps can execute shell commands or invoke actions.
Key Takeaway: GitHub Actions workflows orchestrate jobs that run on runners, where steps execute either shell commands or reusable actions—this layered architecture gives you both simplicity and powerful customization options.