sneak
3eb9f81fc4
Comments and documentation only; the docker build invocation and its flags are untouched, and .dockerignore's effective rules are unchanged. Two prose gaps from review. First, "both flags below must stay" had lost its anchor: it ended a paragraph naming only --no-cache-filter, --target was not introduced until the next one, and three flags follow on the command, so a reader could pick the wrong pair. It now names --target and --no-cache-filter explicitly. Second, the list of things the tooling does not check covered the $stage seam but not .dockerignore, which sits in the same trust boundary and is the more likely thing to be edited — the first review on this change actively suggested extending it for build artifacts. Only what reaches the container is linted, so excluding a Go source there removes it from the lint with no warning. Verified rather than asserted: a planted violation plus that one path in .dockerignore yields `0 issues.` at exit 0 with the violation still in the working tree, while excluding a file other code still references fails loudly on `undefined:` typecheck errors instead. The warning is recorded in script/lint alongside the $stage seam and in .dockerignore itself, where the edit would actually be made.
10 lines
522 B
Plaintext
10 lines
522 B
Plaintext
# The lint build reads the Go sources, go.mod/go.sum and .golangci.yml;
|
|
# none of that comes out of .git, so keep the build context small.
|
|
#
|
|
# This file is part of the lint gate, not housekeeping: only what reaches
|
|
# the container gets linted, so excluding a Go source here silently drops
|
|
# it from the lint (a self-contained file yields `0 issues.` at exit 0 with
|
|
# the violation still in the tree; it fails loudly only if other code still
|
|
# references it). Never exclude Go sources, go.mod/go.sum or .golangci.yml.
|
|
.git
|