Every job on the scotty-git runner is now limited to 1.5 GB of memory
(--memory=1536m, set on the runner) so no workflow can take down the git
server it shares a VM with. When a build step is stopped by that limit,
Kaniko only reports "exit status 137"; the action now prints a clear error
naming the limit and what to do. README gains a "Runner limits" section that
explains exit code 137 for every workflow, not just image builds.
Tested on a temporary branch: a 2 GB step is stopped at ~1.5 GB, the Kaniko
message appears, and a normal build still succeeds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lets any repository on git.scotty-world.com build a Docker/OCI image from its
checked-out code and push it to the registry it chooses (scotty-git's own
container registry, Artifact Registry, Docker Hub, GHCR, ...).
Kaniko instead of docker build: the runner is a shared, long-lived VM, so
giving workflows the Docker daemon would mean root on that machine and image
layers left on its disk. Kaniko builds inside the step's own container: no
root, no privileged mode, nothing left behind. Kaniko v1.23.2 is pinned by
digest.
The action stores no credentials; each repository passes its own secret.
A self-test workflow builds a small image (without pushing) on every change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
