6 Commits

Include renames

Author	SHA1	Message	Date
sneak	236d30bb3c	Correct the build cache wording after review ... REPO_POLICIES.md no longer says a Go test phase's image holds every compiled package; with Go's build cache mounted, those stay in the mount. The comments in script/lint, script/test, script/cibuild and script/docker now say that a new CACHEBUST value reruns the RUN steps only because every stage of the Dockerfile declares ARG CACHEBUST first, and that a stage without the line is served from cache with no warning. NEW_REPO_CHECKLIST.md tells a new repository to add the scripts and every stage's ARG CACHEBUST line in the same commit, in place of re-vendoring them. Model: opus-5-5	2026-10-15 11:56:16 +00:00
sneak	9bd1f006f4	Keep Go's build cache in check builds (closes #113) ... script/lint, script/test, script/cibuild and script/docker pass a new CACHEBUST build argument on every build in place of --no-cache, which empties every cache mount. Every Dockerfile stage declares ARG CACHEBUST first, so every RUN step still runs on every check build. The canonical Go Dockerfile mounts Go's build cache on the steps that compile and runs both go test runs with -count=1, so no test result is reused. REPO_POLICIES.md, both checklists, the Go styleguide and the README say so. A stage without the ARG line is served from cache, so a repository re-vendors the scripts and the ARG lines in one commit. Model: opus-5-5	2026-10-15 09:09:17 +00:00
clawbot	1d9b046b91	Stop the lint and test builds writing an image (closes #123) ... script/lint and script/test build their Dockerfile phase with --output type=cacheonly in place of a tag. The phase still runs uncached and a failing step still fails the build, but no image is written: nothing used those images, and writing one out took about 16 seconds of a Go repository's test build. script/cibuild and script/docker keep their tags. REPO_POLICIES.md, both checklists and the README now say the gate builds write no image. Model: opus-5-5	2026-10-07 12:02:02 +02:00
clawbot	b09fff488b	Assign the image tag on its own line in script/ (closes #101) ... `script/cibuild`, `script/docker`, `script/lint` and `script/test` passed the image tag from `script/projectname` inline in the `docker build` arguments. A failing command substitution inside an argument does not trip `set -e`, so the scripts went on to `docker build` with an empty, `-lint` or `-test` tag, against the rule their own comment states. Each now assigns `tag` on its own line before `docker build`, so the script stops where `script/projectname` fails. The snippets in `prompts/REPO_POLICIES.md` show the same form, and the policy states the own-line rule. Consuming repositories pick this up on their next re-vendor; the defect failed closed. Model: opus-5-5	2026-10-06 02:52:23 +02:00
sneak	c4d5546e86	Gate the build on Docker lint and test phases (closes #40, closes #30) ... Per the owner ruling on issue 40, linting and testing are phases of the main Dockerfile rather than a separate lint file. script/lint and script/test build one phase each by name with caching disabled, and the final stage copies a harmless file from each so the image cannot be built unless both passed. A stage that is not the last is built only when something depends on it or --target names it, so the gates are invoked by name and the edges kept. script/check runs the gates and builds no image of its own; script/cibuild bootstraps first, because CI runs it alone and fmt-check is native. fmt and fmt-check source nvm for the pinned node before calling yarn, which bootstrap installs but leaves off its caller's PATH. Every build in script/ is tagged and uncached. Issue 30 closes too: a container has its own lint cache and lock. Model: opus-5	2026-09-09 11:44:59 +00:00
sneak	3d8d1c0600	Adopt scripts-to-rule-them-all: script/ entrypoints, Makefile shims, policy update (#23) ... Reviewed-on: #23 Co-authored-by: sneak <sneak@sneak.berlin> Co-committed-by: sneak <sneak@sneak.berlin>	2026-07-06 23:53:05 +02:00