
Write a first GitHub Actions workflow: one job on ubuntu-latest that checks the repository out, runs the linter and then the test suite as named steps in that order, records the run summary in a last step, and stops at the first failing command so that a failing test leaves no report and skips every later step.
Rewrite a workflow that navigates with cd into one that declares what each step needs: a job-level defaults.run block for the shared shell and working directory, step-level working-directory and shell overrides for the Python and POSIX shell folders, and two steps that show how the same failing pipe behaves differently under bash and under sh.
Build the check pipeline for a three-folder monorepo: one job on ubuntu-latest that checks the repository out, declares its shared shell and working directory once through defaults.run, checks the bash, Python and POSIX shell folders in order with step-level overrides, compares how the same failing pipe behaves under bash and under sh, writes a check summary last, stops at the first broken check, and contains no cd command.
Learn GitHub Actions hands-on with real workflow runs: triggers, contexts and expressions, job graphs, matrix builds, containers and services, reusable workflows, and pipeline security.
8 modules: Workflow Anatomy & Runners, Triggers & Events, Contexts, Expressions & Variables, Job Orchestration & Conditions, Matrix Strategies, Containers, Services & Artifacts, Reusable Workflows & Custom Actions and Workflow Security.
24 exercises: 9 easy, 12 medium and 3 hard.
Challenges run on Linux CLI.
No. Every challenge runs in a browser-based IDE with everything already set up, and your code is graded automatically against a test suite.