Agent Atlas

Atlas · building

Tests and CI

Checks that run automatically on every change, so a broken commit is caught before anyone ships it.

Established practiceDepth 3 of 4Reviewed 2026-11-12

See it working: Plate II

In plain words

Continuous integration (CI) means a machine builds your code and runs its tests on every change. If something breaks, you find out from the machine, not from a user.

How it works

GitHub describes CI as building and testing code each time you commit, to make sure the commit doesn’t introduce errors. GitHub Actions does this with workflows: YAML files checked into the repository that run on an event such as a push, by hand, or on a schedule.

Going deeper

Agents write code fast, which makes automatic checks more valuable, not less. This site runs its whole test suite before every push, through a hook of the kind Plate II takes apart. See verification.

Sources

  1. Continuous integration GitHub
    • CI using GitHub Actions offers workflows that can build the code in your repository and run your tests.
    • When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors.
  2. Workflows GitHub
    • A workflow is a configurable automated process that will run one or more jobs.
    • Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.

Quotes were checked against the live pages on 2026-11-12.