GitHub Actions

The gate at the loading dock.

CHECKS ITSELF

ON THIS BUILD: USED ON THIS BUILD
WHERE IT RUNS: CI · GitHub Actions · push and pull request
OFFICIAL DOCS: Read the reference →

What it is

A clean GitHub runner that checks the test suite, the type check and the production build on every push to main and every pull request. It is a code gate, not a deploy.

What it does for your business

For your business it means a broken change is caught before a merge, in a clean environment, instead of after a deploy.

Why it earns its place

A check that runs only when someone remembers is a habit, not a gate. Actions runs the same tests on every push and pull request, in a clean environment.

`.github/workflows/ci.yml` is in the repository. It gates code, types and build; the browser design audit and the claims ledger are separate studio gates.

THE TOOL

Open GitHub Actions Read the official docs →

The gate, on every push

USED ON THIS BUILD

Workflow

.github/workflows/ci.yml

Runner

Ubuntu · Node 22

Steps

test · typecheck · build

Deploy

not in CI

The workflow lives in the repository and runs on push and pull request. It gates code, types and build; it does not deploy.

How it runs here

The workflow checks out the repository, installs Node 22 with the npm cache, runs `npm ci`, the test suite, `tsc --noEmit` and the production build. It does not deploy; the deploy remains a separate CLI step after the gate.

THE WORKFLOW

YAML

on:  push: { branches: [main] }  pull_request:jobs:  gate:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - uses: actions/setup-node@v4        with: { node-version: 22, cache: npm }      - run: npm ci      - run: npm test      - run: npm run typecheck      - run: npm run build

When it runs

Every push to main and every pull request. A red job is read before a merge, not after a deploy.

Who owns it

Build owns the workflow. GitHub runs it. QA reads a failed job; the operator owns the repository and its minutes.

What it does not claim

CI gates the code, the types and the build. It does not run the browser design audit or the claims ledger; those run from the studio's docs repository before a release.

THE REFERENCE

The manual above is ours. The vendor's reference is the place to check an API, a version or a limit.

Open the official docs →

This is the tool. The process is what turns it into your business.

File the brief