GitHub Actions

GitHub's built-in CI/CD platform. Runs workflows in response to events like a push, a pull request, or a schedule.

All Dictionary

In one sentence

GitHub Actions is the robot inside my repo that runs a checklist of tasks every time something happens, like a push, a pull request, or a scheduled time of day.

What it is

GitHub Actions is GitHub’s native CI/CD platform. I define a workflow as a YAML file in .github/workflows/, and GitHub executes it on the triggers I specify. Workflows can install dependencies, run tests, build sites, publish packages, open pull requests, or sync design tokens.

Why it matters

Design token pipelines, visual regression checks, and documentation builds all need automation. GitHub Actions is where that automation usually lives, because it sits next to the code and needs no extra service account. If my repo is on GitHub, Actions is the lowest-friction place to automate anything.

Example

A minimal workflow that runs on every push to main:

name: Sync Tokens
on:
  push:
    branches: [main]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 20 }
      - run: npm ci
      - run: npm run build:tokens
      - run: npm run publish:tokens
        env:
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

Every push to main now rebuilds and republishes tokens without a human touching it.

When to use it

  • You want to automate token builds, visual tests, or docs publishing
  • You need a scheduled job (nightly audits, weekly reports)
  • You want pull requests to trigger checks before they can merge
  • You need to pass secrets like API keys into automated jobs

See also