Build once, deploy everywhere
Uploading the artifact once and promoting it removed a whole class of works in staging but not in production bugs.
Browse
Build fast, secure workflows that test every pull request, publish artifacts and deploy to staging and production with approvals and OIDC
Created by Rahul Menon
Continuous integration and delivery is where a team's habits become visible: every pull request tested, every merge deployable, every release traceable. GitHub Actions makes that achievable without running your own CI servers. This course teaches you to write workflows that are fast, readable and secure.
Starting from a sample web application, you will build a pipeline step by step:
CI systems hold the keys to production, which makes them an attractive target. We cover the permissions of the built in token, pinning third party actions, the risks of workflows triggered by forks, and how to handle secrets. These lessons draw on real supply chain incidents that affected popular actions.
The examples use a Node.js application, with notes for Python and Go. You need a free GitHub account; everything runs on GitHub hosted runners.
DevOps engineer teaching GitHub Actions and Terraform for small teams that ship every day
I help teams move from manual releases to pipelines they trust. Most of my work is GitHub Actions workflows, Terraform modules and the review habits that keep both maintainable.
I teach CI/CD and infrastructure as code as everyday engineering, not as a separate specialism. That means readable YAML, small reusable pieces, secrets handled properly and plans that a reviewer can understand in two minutes.
Every course uses a sample repository you fork and change. You will break the pipeline on purpose, read the logs and fix it, because that is the skill you will use most.
Uploading the artifact once and promoting it removed a whole class of works in staging but not in production bugs.
Caching, concurrency and test sharding cut our pull request feedback time dramatically. Clear examples throughout.
Pinning actions by SHA and fixing script injection were things nobody on my team knew about. We changed every workflow.
We now maintain one shared CI workflow for thirty repositories, versioned with tags as shown.
Environments with approvals plus OIDC to AWS gave us a proper audit trail. A bit Node focused for our Python team.
I started knowing nothing about Actions. The log reading lesson alone saved me many hours.
Accurate and well organised. Some early lessons repeat what is in the official documentation, but later sections add a lot.