0: Introduction

Introduction to the course

•Course Overview

1: History and Motivation

History of continuous integration tools

•History and Motivation

2: Why GitHub Actions?

Comparison of GitHub Actions with competitors

•Why GitHub Actions?

•System Set Up

3: Core Features

Deep dive into workflow syntax, triggers, and job configuration

•Workflow Anatomy

•Jobs and Triggers

•Variables and Data Flow

•Secrets and Next Steps

4: Advanced Features

Explore matrices, reusable workflows, and composite actions

•Runner Types and Execution Environments

•Persisting Build Outputs with Artifacts

•Reusing Work with Caches

•Controlling GitHub Permissions

•Authenticating to Third-Party Systems

•Matrix Strategies, Conditionals, and Concurrency Controls

5: Marketplace Actions

Discover and integrate community actions from the GitHub Marketplace

•Marketplace Actions

6: Authoring Actions

Build custom JavaScript and Docker actions from scratch

•Authoring Actions Overview

•Composite Actions

•Reusable Workflows

•JavaScript and TypeScript Actions

•Container Actions

•Workflow Commands and Runner State

•Authoring and Sharing Your Actions

7: Common Workflows

Implement CI/CD pipelines for typical application stacks

•Common Workflows

8: Developer Experience

Optimize logs, secrets, environments, and permissions for teams

•Developer Experience (Actions)

•Developer Experience (Workflows)

•Debugging and Observability

9: Best Practices

Harden workflows with security, reliability, and cost-saving techniques

•Performance Best Practices

•Maintainable Workflow Patterns

•Monorepo vs. Multirepo Considerations

•Security Best Practices

10: Capstone Project

Apply course concepts by automating a real-world deployment pipeline

•Capstone Overview

•Unified Test Workflow

•Build and Deploy Workflows

•Repo Automations

•Migrating to Namespace

11: Course Wrap Up

Final words about the course.

•Course Wrap Up

Video Thumbnail for Lesson

10.5: Migrating to Namespace

Scaling with Namespace Cloud runners

So far, we have used the GitHub hosted runners throughout the capstone.

This lesson shows how easy it is to move to Namespace for reduced costs and improved performance.

The general process is:

Replace every runs-on: ubuntu-24.04 with labels such as runs-on: ["namespace-cloud-ubuntu-24.04-amd64-4x16"] (CPU x memory).
Remove the QEMU/Buildx setup steps in favor of Namespace remote builders.
Define cache volumes per service via runner labels (e.g., appending cache and cache-tag:${{ matrix.cache_label }}) and configure the custom namespace-cloud/cache-action to persist Go modules, NPM artifacts, and Poetry environments.

These changes roughly halve runner costs while cutting build times thanks to warm caches and native ARM/AMD64 builders.

< Prev: Repo Automations Next: Course Wrap Up >