- Berlin, Deutschland
- https://sneak.berlin
- Joined on
2020-02-05
Block a user
DECISION NEEDED: should pinned Go tools be
go install-with-commit-pin, or tracked as go.mod tool dependencies?
commit pinned installation, not pulled into deps.
DECISION NEEDED: canonical
script/bootstrap pins NODE_VERSION and YARN_VERSION but policy tells it to skip on any version found — the pins are decorative
Decision: vmsetup and secpol are tracked projects with no repo on the instance
canonical .golangci.yml emits a gomodguard deprecation warning under golangci-lint v2.12+
Migrate canonical .golangci.yml to gomodguard_v2, with a block list
script/lint shares one golangci-lint cache across all concurrent sessions, producing cross-contaminated results
canonical .dockerignore omits .claude/, so agent worktrees land in the Docker build context
SECURITY: canonical .dockerignore does not exclude .env, *.pem or *.key, so local secrets ship into the Docker build context
script/bootstrap installs the pinned golangci-lint only
if missing, so version pins are inert on any machine that already has the tool
script/cibuild reports a green it did not earn: Docker serves the
make check layer from cache
All linting must run in Docker: canonicalise homoicon's Dockerfile.lint + script/lint pattern
Milestone next: check-cache busting, build-context hygiene, lint in a container
Add -count=1 to the canonical Go make test example