zeekay e1c4e4876b perf(runner): the image carries the actions build.yml names, cloned ...

A forge runner lives one job and began each with an empty act cache, and
act clones an action with go-git, full history, before the first step:
forge run 16634 spent 156 of each job's 161 s of setup cloning
setup-node (72 s), setup-go (42 s), setup-bun (20 s) and checkout
(17 s), the three it then skipped included.

The image now clones each into ~/.cache/act/<sha256 of the uses string>
with every ref the remote advertises, so the runner opens it and fetches
what moved since the build. Timed with act's own clone executor: 0.2 to
1.1 s each, against 2 to 90 s cold; with the branches and tags alone it
still fetched every pull request's objects, 10 to 40 s each. It adds
some 340 MB to the image.

hanzo.yml's runner-preseeds fails when build.yml names an action the
image does not carry.

2026-10-20 08:05:25 -07:00

..

Dockerfile

perf(runner): the image carries the actions build.yml names, cloned

2026-10-20 08:05:25 -07:00

runner

The runner is git-runner, and it reads GIT_RUNNER_*

2026-09-16 13:33:03 -07:00

VERSION

Bake the toolchain into the runner image

2026-09-24 10:12:10 -07:00