GitHub Actions · zero to on-call
Pipelines you
can trust.
Workflows, caching, secrets and environments, learned by fixing pipelines that break, from the first build to safe deploys.
Learning GitHub Actions?
Start from zero, step by step.
Levels in order, each with a broken pipeline to fix in your browser.
Something broken right now?
Paste the error, get the fix.
The cause, the commands to confirm it and the fix, for every common Actions error.
Everything you need, from the first workflow to the 3 a.m. incident.
Run workflows here.
Empty secrets, cache misses, permissions denied, deploys that race. Edit the YAML, send an event, read the run.
Every key, explained.
Triggers, permissions and matrices, and every risky pattern: injection, unpinned actions, pwn requests.
Know why, not just how.
Every answer explained.
From event to deploy.
Each part, and how it fails.
Learn why it happens, then practise the fix.
Fix a broken pipeline. Right here.
Real incidents, real error messages. No install, no account.
Practise on real runners, free
Your own fork
Public repositories run on GitHub-hosted runners at no cost.
# 1. Fork and clone the course
gh repo fork SandeepKomal/GitHub-Actions --clone
cd GitHub-Actions
# 2. Enable Actions on the fork, then push
git commit --allow-empty -m "Run CI"
git push
# 3. Watch the run
gh run watchWhat is in the repository
Working workflows and deployment templates the levels use.
- ci.yml: a Python matrix with a pip cache, pinned actions
- security.yml: CodeQL on a schedule
- reusable-ci.yml: a reusable workflow
- examples/: Kubernetes, Swarm and Maven deploy templates
Your path
Progress is saved in this browser only. Tick a level when you have done its lab.
Quiz
Questions from real incidents, several for every level. You see right or wrong at once, with the reasoning.
Workflow X-ray
Paste a workflow to see what every key does, which lines are risky, and what is missing. Or open one of this repository's own.
Stuck on an error?
Paste the error from your run, or pick a symptom. Each answer explains what the error means, then each likely cause with a check that proves it and its fix, then gives you a safe scenario to break and fix it yourself, so you recognise it next time.
Every answer is also on the problems page, plain HTML that works without JavaScript.
Cheat sheet
The workflow snippets and gh commands people use. Try opens the playground scenario where it applies; Lab marks what needs a real repository.
How a workflow run works
How a run goes from an event to a deploy: what each part does and how you can tell when it breaks. Point at a part, or tab to it.