---
summary: Run CI workflows with Forgejo Actions; every job runs in a fresh ScaiBunker
  microVM with a closed network.
title: Actions
path: guides/actions
status: published
---

# Actions

ScaiGit runs CI with Forgejo Actions, which uses GitHub Actions' workflow
syntax. Every job runs in its own **ScaiBunker**: a fresh microVM created for
that job and destroyed when it ends. Nothing carries over between jobs, and a
job can reach only a short list of package sources.

## Your first workflow

Add a file under `.forgejo/workflows/` (or `.github/workflows/`), for
example `.forgejo/workflows/ci.yml`:

```yaml
on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: python3 -m pip install -r requirements.txt
      - run: python3 -m pytest
```

Push it. The run appears under the repository's **Actions** tab, with live
logs per step.

## Choosing a machine size

`runs-on` picks the size of the microVM:

| `runs-on` | CPU | Memory | Disk |
|---|---|---|---|
| `scaibunker-small` | 1 | 2 GiB | 10 GiB |
| `scaibunker-medium` | 2 | 4 GiB | 20 GiB |
| `ubuntu-latest`, `ubuntu-24.04` | 2 | 4 GiB | 20 GiB |
| `scaibunker-large` | 4 | 8 GiB | 30 GiB |

A job with a label ScaiGit doesn't serve stays queued.

## What's in the machine

Ubuntu 24.04 with git and git-lfs, Node.js 22 with npm, Python 3 with pip and
venv, build-essential, curl, wget, jq, zip and zstd. Jobs run as the user
`ci`, who can use `sudo`.

**Containers:** Podman is installed, rootless and rootful, and the `docker`
command maps to it. `docker build`, `docker run` and image pulls work.

## Network

A job can reach its own ScaiGit instance and these sources, and nothing else:

| What | Hosts |
|---|---|
| Actions such as `actions/checkout` | `data.forgejo.org`, `code.forgejo.org` |
| Ubuntu packages | `archive.ubuntu.com`, `security.ubuntu.com` |
| Python | `pypi.org`, `files.pythonhosted.org` |
| JavaScript | `registry.npmjs.org` |
| Go modules | `proxy.golang.org`, `sum.golang.org`, `storage.googleapis.com` |
| Rust crates | `crates.io`, `index.crates.io`, `static.crates.io` |

Anything else, including `github.com`, does not resolve. Short action names
such as `actions/checkout@v4` are fetched from Forgejo's mirror at
`data.forgejo.org`, so they work; a full `https://github.com/...` action
reference does not. If your build needs another source, ask your
administrator.

## Secrets

Repository and organisation secrets (**Settings → Actions → Secrets**) are
passed to jobs as usual. Short-lived credentials issued per job by ScaiVault
are planned, so that long-lived secrets need not be stored in ScaiGit at all.

## Not supported yet

- `container:` on a job and `services:`. Use Podman inside the job instead.

## Cancelling

Cancelling a run in the web interface marks its jobs cancelled at once; their
microVMs are destroyed within about two minutes.
