Latchkey Learn
CI Concepts: Reliability, Security & Terms
Self-healing CI, ephemeral runners, reliability, security and the reference pages every GitHub Actions user needs to understand their pipeline.
Concepts
A complete pipeline exampleA complete CI/CD pipeline example for GitHub Actions, explained stage by stage, including the gates and cache
Making a pipeline reliableCI pipeline reliability is a ratio, not a pass rate. The four numbers worth tracking on GitHub Actions, and
What ephemeral runners areEphemeral runners take one GitHub Actions job and are destroyed.
Exit codes and signalsExit codes in CI from 0 to 143: what each number means on a GitHub Actions runner, what causes it, and the
Deprecations trackerGitHub Actions deprecations with the date each one takes effect: runner images, moving labels, Node 20
Runner specs by sizeGitHub Actions runner specs for every size: vCPU, RAM and disk for standard, larger, macOS and ARM runners,
CI security for GitHub ActionsGitHub Actions security in six controls: token scopes, SHA pins, pull_request_target, fork secrets, OIDC and
What self-healing CI isSelf-healing CI repairs a failing GitHub Actions step mid-job.
What is a runner?What is a GitHub Actions runner? The machine that executes a job: hosted, self-hosted or managed, how runs-on
Installed softwareWhat is installed on ubuntu-latest today: the GitHub Actions image versions, what is missing, and how to
Explore other topics
GitHub Actions runners comparedEvery managed runner vendor, priced and benchmarked side by side.
GitHub Actions costWhat Actions really costs, and how to cut it.
Runner failures Latchkey repairsOut of memory, disk full, rate limits, lost runners: reproduced and fixed.
GitHub Actions workflow errorsWorkflow, YAML, permissions and artifact errors, diagnosed and fixed.
Docker in CI: Registry, Build & RuntimeRegistry, runtime and build errors on CI runners.
Faster GitHub ActionsCaching, parallelism and cold starts, measured.