Command Palette

Search for a command to run...

Hectal
Phase 2Intermediate3 of 9 in CI/CD

GitHub Actions

Workflows, secrets, reusable pieces, and your own runners — going from Topic 0.4's minimal example to genuinely production-grade GitHub Actions usage.

Phase 0 got one minimal GitHub Actions workflow running. This phase goes deep on the platform itself: the exact vocabulary of workflows/jobs/steps/actions, handling secrets and multiple environments safely, avoiding copy-pasted YAML across repositories, and running your own infrastructure when hosted runners aren't enough.

0/4 · 0%
4 topics ~54 min 9 code blocks & diagrams
Start with the first topic
1
2.1

Workflows, Jobs, Steps, and Actions

GitHub Actions' own vocabulary maps directly onto Phase 0.2's universal pipeline model — a workflow is the pipeline, jobs are its stages' work, steps are individual commands, and actions are reusable building blocks anyone can publish.

13 min 1 diagram 1 code practice

2
2.2

Secrets & Environments

GitHub Actions Secrets keep real credentials out of your workflow YAML entirely, and Environments add approval gates and environment-specific secrets on top — the same never-commit-a-real-credential lesson, applied to pipeline configuration.

14 min 1 diagram 1 code practice

3
2.3

Reusable Workflows & Composite Actions

Copy-pasting the same YAML across many repositories is the same anti-pattern Helm's own course warned against for Kubernetes manifests — reusable workflows and composite actions are how you define a pattern once and share it everywhere.

14 min 1 diagram 2 code practice

4
2.4

Self-Hosted Runners

A hosted runner is fresh, disposable infrastructure GitHub manages for you — a self-hosted runner is your own machine instead, needed when a job requires specific hardware, network access, or software hosted runners can't provide.

13 min 1 diagram 1 code practice