sneak/prompts
1
0
Fork 0
Code Issues 5 Pull Requests 2 Actions 1 Packages Projects Releases Wiki Activity

Keep Go's build cache in check builds (closes #113) #129

Merged
clawbot merged 4 commits from issue-113-keep-go-build-cache into next 2026-10-15 16:50:31 +02:00
Conversation 7 Commits 4 Files Changed 11
+3 -3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit ae3bef5362 - Show all commits
prompts/REPO_POLICIES.md
+3 -3
View File
@@ -280,9 +280,9 @@ style conventions are in separate documents:
check builds, and Go reuses one only when all its inputs are unchanged, so check builds, and Go reuses one only when all its inputs are unchanged, so
it saves the compile without skipping a check. Nothing else is kept: it saves the compile without skipping a check. Nothing else is kept:
golangci-lint's own cache would replay stored findings in place of a lint golangci-lint's own cache would replay stored findings in place of a lint
run, and the module cache would skip downloading the modules and checking run, and the module cache would skip downloading the modules. Go's build
them against `go.sum`. Go's build cache also holds test results, which is cache also holds test results, which is why both `go test` runs carry
why both `go test` runs carry `-count=1`. `-count=1`.
- If the project uses `//go:embed` directives that reference build artifacts - If the project uses `//go:embed` directives that reference build artifacts
(e.g. a web frontend compiled in a separate stage), the lint phase must (e.g. a web frontend compiled in a separate stage), the lint phase must
create placeholder files so the embed directives resolve. Example: create placeholder files so the embed directives resolve. Example: