MMB faculty talk (15 min)

2026-10-02

Forgejo CI

Enable Actions in the repository settings. Register a Forgejo runner with a Docker-capable ubuntu-latest label (for example, ubuntu-latest:docker://node:22-bookworm). Both workflows use the node:22-bookworm job container and install their build dependencies there; they do not require Typst or fonts on the runner host. Network access to GitHub (Typst, fonts, and submodules) and data.forgejo.org (actions) is required.

Repository Actions secrets:

• RELEASE_TOKEN: Forgejo access token with repository write access for creating releases and uploading/replacing attachments. Limit it to this repository where supported.
• COMMENT_TOKEN (optional): Forgejo access token with permission to write issue/PR comments. Without it, preview builds still upload artifacts. Fork PRs never run the comment step or receive this token.

Pushes to main and pull requests produce PDF and title-slide preview artifacts (retained for 14 days). Release creation builds the release tag and attaches the PDF, PNG, source archive (including submodules), and checksums. Manual release runs require an existing tag; they create a release if needed. Re-running a release replaces matching attachments while preserving its title and notes.

The GitHub-hosted submodules are fetched over HTTPS instead of SSH. If any are private, configure GitHub read credentials separately; a Forgejo token cannot authenticate to GitHub. No runner configuration or registration token is stored in this repository.