👷 Add CI: Rust and frontend checks #4

Merged

mat merged 3 commits from ci-rust-frontend into main

2026-10-02 07:28:39 +00:00

mat commented

2026-10-01 13:54:50 +00:00

Owner

Context

The MVP is on main but nothing verifies it automatically — make test only runs if someone remembers to. This adds Forgejo Actions CI, matching the runner setup already proven on this instance (ubuntu-latest, Docker execution, per-job container: images).

What it does

Two jobs in .forgejo/workflows/ci.yml, triggered on PRs to main, pushes to main, and manual dispatch (redundant runs on the same PR are cancelled):

rust (rust:1, same major version as the Dockerfile): rustup component add rustfmt clippy, cargo fmt --check, cargo clippy --all-targets -- -D warnings, cargo test
frontend (node:22, same as the Dockerfile): npm ci, npm run check (svelte-check + tsc), npm test (vitest), npm run build

E2e (Playwright) follows in a stacked PR — it needs a small config change to run on the CI image's Chromium.

Considerations

The rust job clones by hand instead of actions/checkout: JS actions run node inside the job container (confirmed on this runner: exit 127), and the official Rust image has no Node. git ships in rust:1 and the repo is public, so a plain clone of github.head_ref || github.ref_name works for PRs, pushes, and manual dispatch. Caveat: PRs from forks of this repo wouldn't resolve — fine for a solo project.
rustup component add rustfmt clippy is needed because current rust: images ship a minimal toolchain.
No caching yet; if the Rust job turns out slow we can add cache in a follow-up.

## Context The MVP is on `main` but nothing verifies it automatically — `make test` only runs if someone remembers to. This adds Forgejo Actions CI, matching the runner setup already proven on this instance (`ubuntu-latest`, Docker execution, per-job `container:` images). ## What it does Two jobs in `.forgejo/workflows/ci.yml`, triggered on PRs to main, pushes to main, and manual dispatch (redundant runs on the same PR are cancelled): - **rust** (`rust:1`, same major version as the Dockerfile): `rustup component add rustfmt clippy`, `cargo fmt --check`, `cargo clippy --all-targets -- -D warnings`, `cargo test` - **frontend** (`node:22`, same as the Dockerfile): `npm ci`, `npm run check` (svelte-check + tsc), `npm test` (vitest), `npm run build` E2e (Playwright) follows in a stacked PR — it needs a small config change to run on the CI image's Chromium. ## Considerations - **The rust job clones by hand instead of `actions/checkout`**: JS actions run `node` inside the job container (confirmed on this runner: exit 127), and the official Rust image has no Node. `git` ships in `rust:1` and the repo is public, so a plain clone of `github.head_ref || github.ref_name` works for PRs, pushes, and manual dispatch. Caveat: PRs from forks of this repo wouldn't resolve — fine for a solo project. - **`rustup component add rustfmt clippy`** is needed because current `rust:` images ship a minimal toolchain. - No caching yet; if the Rust job turns out slow we can add cache in a follow-up.

mat added 1 commit

2026-10-01 13:54:50 +00:00