2 Commits

Author SHA1 Message Date
577b29db39 Add Gitea Actions pipeline that builds and publishes the image
Some checks failed
build / container (push) Failing after 14s
Runs on pushes to master, tag pushes and pull requests:

  * the Dockerfile's new `test` stage runs the whole suite, so a failing
    test stops the image from being built or pushed at all
  * the image builds with plain docker rather than the buildx and login
    actions, so a job never has to reach the internet to fetch third-party
    actions -- the most common way a self-hosted runner fails
  * it pushes to this instance's registry, deriving the host from
    github.server_url instead of hardcoding it

Tags published: `latest` and the branch or tag name (only master moves
`latest`), plus an immutable sha-<short> so an image can be traced back to
its commit.  Pull requests build but never push, so a fork cannot publish
into the registry.

Two things the gate caught once it ran inside a container:

  * the suite reads config.example.json from the repository root, a hidden
    dependency that would have failed the first pipeline run
  * `[ "$ref_name" = "$DEFAULT_BRANCH" ]` under `set -u` would have aborted
    every branch build if that env key were ever renamed; it now has an
    inline fallback

`make test-docker` runs the same gate locally, and README.md documents what
the runner needs: docker reachable from the job, and a token allowed to
write packages.

Also untrack .pi/, which holds pi session task output rather than project
files, and ignore it.
2026-11-15 18:20:36 -05:00
b76aea2899 Initial commit 2026-11-15 18:15:03 -05:00