GitHub Actions

Build CI/CD pipelines with GitHub Actions: workflows, secrets, matrix builds, and cloud deploys.

Chapter 1: GitHub Actions Basics

YAML workflows live in .github/workflows; jobs run on runners.

Note: Expand this section with your own examples and production notes.

push, pull_request, schedule, and workflow_dispatch.

Note: Expand this section with your own examples and production notes.

Reuse community actions; pin versions with commit SHA for security.

Note: Expand this section with your own examples and production notes.

Run unit and integration tests on every PR.

name: CI
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm test

Note: Expand this section with your own examples and production notes.

Build artifacts once; promote the same build across environments.

Note: Expand this section with your own examples and production notes.

GitHub Environments add approval gates and environment secrets.

Note: Expand this section with your own examples and production notes.

Test multiple Node or Python versions in parallel.

Note: Expand this section with your own examples and production notes.

actions/cache speeds dependency installs.

Note: Expand this section with your own examples and production notes.

Store tokens in repo or org secrets; never log secret values.

Note: Expand this section with your own examples and production notes.

Use OIDC federation instead of long-lived access keys.

Note: Expand this section with your own examples and production notes.

kubectl apply or Helm upgrade from CI with kubeconfig secrets.

Note: Expand this section with your own examples and production notes.

Slack or email on failure; publish test and coverage reports.

Note: Expand this section with your own examples and production notes.