All checks were successful
check / check (push) Successful in 23s
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 — template-app-go's ordering trick, extended to the test phase. 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; script/cibuild bootstraps first, because CI runs it alone and fmt-check is native. Every build in script/ is tagged and uncached. No config verify step. Issue 30 closes too: a container has its own lint cache and lock. Model: opus-5
949 B
Executable File
949 B
Executable File