Before stepping onto the factory floor, make sure you have these tools and concepts in place. Don't worry — we'll explain everything else from scratch.

CI/CD stands for Continuous Integration and Continuous Delivery/Deployment. Think of it as an automated factory line for your code.

GitHub Actions is GitHub's built-in automation platform. You write small recipe files (called workflows) that tell GitHub what to do when events happen — like pushing code, opening a pull request, or clicking a button.

Every workflow is a YAML file stored in .github/workflows/. YAML uses indentation (spaces, not tabs) to show structure — like an indented factory org chart.

# Name shown in the Actions tab
name: CI Pipeline

on:                    # WHEN the line starts
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:                   # Work stations
  build-and-test:       # Job ID
    runs-on: ubuntu-latest  # Runner machine
    steps:                # Robot tasks
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
      - run: npm ci
      - run: npm test

Let's build a real workflow step by step. We'll create a simple CI pipeline for a Node.js project.

1. 1

   Create the workflows folder

   In your repo root, create .github/workflows/ci.yml. The dot-folder is required — GitHub looks there automatically.

2. 2

   Define the trigger

   Use on: push to run on every push, or limit to specific branches to save factory resources.

3. 3

   Add checkout & setup steps

   Always start with actions/checkout@v4 to copy your code onto the runner. Then install your language runtime.

4. 4

   Run your build & tests

   Use run: for shell commands. If any step fails, the whole job stops — the red light turns on.

5. 5

   Commit, push, and watch

   Go to your repo's Actions tab. You'll see a yellow (running), green (success), or red (failure) indicator for each run.

name: My First CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test
      - run: npm run build

Your factory handles sensitive materials — API keys, passwords, tokens. Never put these in your workflow file. GitHub provides a secure vault.

jobs:
  deploy:
    runs-on: ubuntu-latest
    environment: production    # triggers protection rules
    steps:
      - uses: actions/checkout@v4
      - name: Deploy to cloud
        env:
          API_KEY: ${{ secrets.DEPLOY_API_KEY }}
          REGION:  ${{ vars.AWS_REGION }}
        run: ./deploy.sh

Every factory needs dashboards and alarm bells. GitHub Actions gives you multiple ways to gauge whether your pipeline is healthy.

Built-in GitHub UI

• Actions tab — see all workflow runs with ✅ success, ❌ failure, 🟡 in-progress, or ⏸ cancelled status.
• Job logs — click any run to expand steps and read stdout/stderr output line by line.
• Annotations — tools like linters can attach inline comments on the exact file and line that failed.
• Workflow badges — embed a status shield in your README: ![CI](https://github.com/user/repo/actions/workflows/ci.yml/badge.svg)

Programmatic Access & Metrics

GET /repos/{owner}/{repo}/actions/runs
GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs

# Key fields in response:
# status: "completed" | "in_progress" | "queued"
# conclusion: "success" | "failure" | "cancelled" | "skipped"

- name: Set result
  id: check
  run: echo "passed=true" >> $GITHUB_OUTPUT

- name: Fail with message
  run: echo "::error file=app.js,line=10::Tests failed"

- name: Summary report
  run: echo "## Test Results" >> $GITHUB_STEP_SUMMARY

Example: Python + Docker Deploy

name: Python CI/CD

on:
  push:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: '3.12'
      - run: pip install -r requirements.txt
      - run: pytest

  docker:
    needs: test
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'
    steps:
      - uses: actions/checkout@v4
      - uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKER_USER }}
          password: ${{ secrets.DOCKER_TOKEN }}
      - uses: docker/build-push-action@v5
        with:
          push: true
          tags: myapp:latest

Common Failures & Fixes