GitHub Actions from Zero to Ten Production Workflows: A Beginner's Map
GitHub Actions has become the default automation layer for hosted repos, and the real cost of learning it is trial-and-error: the Pages 403 failure is nearly always the missing id-token permission, and the difference between pull_request and pull_request_target is a known secret-leak vector. This guide compresses both into copy-paste templates.
An event-driven automation platform runs any command sequence when a repo event fires. The core mental model: an event triggers a workflow, a workflow contains jobs, each job runs on its own fresh runner and each job is a list of steps that either execute shell commands or call reusable actions. This guide is built entirely around that five-term mental model, from the first `.github/workflows/` file through reading logs and troubleshooting. Checkout must precede any command that needs repo files because runners start empty.
Ten scenario configs make up the practical core: GitHub Pages deployment with the three required permissions, Vercel and Netlify deploys via secrets, a Node.js CI with a version matrix and a Postgres service container, monorepo builds gated by paths-filter and Turborepo, Docker images pushed to GHCR with OIDC-style GITHUB_TOKEN, SSH and rsync VPS deploys, PR automation with labeler, cron data sync, tag-triggered npm publishing with provenance, and reusable workflows via workflow_call.
The five-term mental model is presented as the entire foundation: every later section, including the ten scenarios, is framed as an expansion of event/workflow/job/step/runner relationships.
The 90% Pages failure diagnosis is the most actionable claim in the guide, identifying a specific permission configuration rather than a vague deployment issue.
portraying `pull_request` vs `pull_request_target` as a security boundary rather than a YAML detail reflects a real fork-pr privilege distinction that teams often discover only after an incident.
The guide's repeated insistence on `--frozen-lockfile` addresses the class of bugs where local and CI environments diverge, treating dependency drift as a CI failure mode, not just a reproducibility concern.
The progression from copy-paste configs to a security hardening checklist shows that pipeline maintenance is as much about dependency pinning and secret hygiene as about writing working YAML.
I really agree with those security reminders, especially that once a secret is written in, even deleting it counts as a leak — nine out of ten beginners will fall into that trap. When I first started, I also took the shortcut and hardcoded keys, and later I had to go through the painful rotation of everything; I was so frustrated I couldn't even cry.