> ## Documentation Index
> Fetch the complete documentation index at: https://tesser.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Run GitHub Actions jobs on Tesser boxes

> Connect a GitHub organization once, set runs-on to a Tesser label, and each job runs on its own box starting from its last successful run's disk.

Tesser can run your GitHub Actions jobs. Each job gets its own new box, and
the box starts from the disk the job's last successful run left behind: the
checkout, the home directory with its package stores and build caches, the
tool cache, and Docker's images and layers. Installs and builds then redo
only what changed.

GitHub Actions on Tesser is not open to every org yet. Tesser turns it on
org by org, and `tesser ci connect` is refused in an org where it is not on
([who can use it](https://tesser.sh/docs/reference/boxes.md#who-can-use-them)).

## Connect a GitHub organization

An admin of the Tesser org runs this once:

```sh theme={"theme":"css-variables"}
tesser ci connect
```

It prints a link. Someone who owns the GitHub organization opens it and
installs the Tesser GitHub App there. After that, jobs in the GitHub
organization's repositories can run on the Tesser org's boxes.

## Run a job on Tesser

Point a job's `runs-on` at a Tesser label:

```yaml theme={"theme":"css-variables"}
jobs:
  test:
    runs-on: tesser-4vcpu
    steps:
      - uses: actions/checkout@v4
        with:
          clean: false
      - run: npm ci
      - run: npm test
```

The number in the label is the box's vCPU count. Nothing else in the
workflow has to change. `clean: false` keeps untracked files such as
`node_modules` in the checkout between runs; without it, `actions/checkout`
deletes them, and only what lives outside the checkout carries over.

The box is removed when the job ends and is billed by the second, like any
box.

## See what your jobs did

```sh theme={"theme":"css-variables"}
tesser ci                                  # connected organizations and the latest jobs
tesser snapshot rm <snapshot_id>           # drop a job's saved disk
```

`tesser ci` shows which disk each job started from, or why it started cold.
To run a job on a clean disk, use the label with `-no-snapshot`, such as
`runs-on: tesser-4vcpu-no-snapshot`.

[GitHub Actions jobs](https://tesser.sh/docs/reference/boxes.md#github-actions-jobs) has the exact
rules: the labels and sizes, which branch or pull request a job reads and
saves, forks, and how long a job's disk is kept.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.