Why Bones

CI/CD

Lint, tests, builds, accessibility, and security checks on every pull request, only for what changed — and a production deploy on every merge.

The problem

A starter without tests is one you're afraid to change. A pipeline that runs everything on every commit is one people learn to ignore.

What Bones does

Every pull request runs GitHub Actions, with jobs in parallel:

  • Lint and format — oxlint, Prettier, and syncpack for dependency versions.
  • Generated files — migrations, the auth schema, email tokens, and brand assets must match their sources.
  • Backend tests — Vitest against a real, throwaway Postgres.
  • Storybook tests — every component and page story, in real Chromium.
  • Builds — the web app, marketing site, blog, and docs. The builds are the typecheck.
  • Accessibility — the sweep described in Accessibility.
  • Security — Semgrep, ZAP, the CSP check, and the secrets check described in Security.

It stays fast:

  • Only what changed. Each job runs when its files, or a workspace it imports, changed. A docs change doesn't start Postgres.
  • Drafts run nothing. A draft is work in progress, so CI waits until it's marked ready and then runs everything.
  • A new push cancels the old run on the same pull request.
  • Dependencies are cached. node_modules and Playwright's Chromium are restored from cache, and main keeps the cache warm.

Each build is kept for three days, so you can download what a pull request produced.

A pull request can't merge into main until its checks pass.

Every merge deploys

Merging to main is the go-ahead. deploy.yml builds the backend image and the four sites, deploys the AWS infrastructure, runs migrations, releases the new backend, publishes the sites, and smoke-tests every hostname. A run takes 9 to 15 minutes.

  • No keys in GitHub. Each run signs in to AWS with a short-lived OIDC token, through a role that only trusts this repo's production environment.
  • A broken build changes nothing. Every site builds before the first AWS step.
  • Open tabs keep working. Hashed files from earlier deploys stay published, so a tab loaded before a deploy can still fetch its chunks.
  • One at a time. Deploys queue, and a running one is never cancelled.
  • Rollback is a rerun. Rerunning an earlier deploy puts that commit's backend and infrastructure back.

What isn't done yet

  • No approval step. GitHub only offers required reviewers on a private repo with Enterprise, so merging deploys.
  • One environment. There's production and your machine. Staging is planned, not built.
  • The desktop app isn't built in CI. A Tauri build needs Rust and system libraries, which is its own workflow.

How it compares

Most starters ship a lint script and an empty test folder. Bones ships a suite that already covers auth, permissions, organizations, and storage, so the first thing you add has something to lean on.

Go deeper

  • GitHub Actions — why the pipeline is built this way.
  • CI/CD — the jobs, adding one, and how a deploy runs.
  • Testing — running the tests yourself.