.dockerignore gains /*.test and /*.out in the repository's own section, after the shared content, and its comment there names them. A Go test binary or coverage file left at the repository root, which .gitignore already ignores, went into the build context of every docker build in script/ and was copied into the lint, test and build stages, where the existing-repo checklist asks that such files be kept out.
Checked by enumerating a probe image, as REPO_POLICIES.md asks: a Dockerfile that copies the whole context, built once with the old .dockerignore and once with the new, with x.test and x.out planted at the root and two directories down. The two listings differ only in the root x.test and x.out, which the new one no longer has. The probe images and planted files are removed.
Judgement call: the entries match only at the root, as the issue and the checklist ask, so the same files in a subdirectory still reach the image (the probe shows this). The Go module is at the root, where go test -c and -coverprofile write when run from there.
Model: opus-5-5
Closes https://git.eeqj.de/sneak/netwatch/issues/155.
`.dockerignore` gains `/*.test` and `/*.out` in the repository's own section, after the shared content, and its comment there names them. A Go test binary or coverage file left at the repository root, which `.gitignore` already ignores, went into the build context of every `docker build` in `script/` and was copied into the lint, test and build stages, where the existing-repo checklist asks that such files be kept out.
Checked by enumerating a probe image, as `REPO_POLICIES.md` asks: a Dockerfile that copies the whole context, built once with the old `.dockerignore` and once with the new, with `x.test` and `x.out` planted at the root and two directories down. The two listings differ only in the root `x.test` and `x.out`, which the new one no longer has. The probe images and planted files are removed.
Judgement call: the entries match only at the root, as the issue and the checklist ask, so the same files in a subdirectory still reach the image (the probe shows this). The Go module is at the root, where `go test -c` and `-coverprofile` write when run from there.
Model: opus-5-5
A Go test binary or coverage file left at the repository root, which
.gitignore already ignores, went into the build context of every docker
build in script/ and was copied into the lint, test and build stages.
The repository's own section of .dockerignore now lists /*.test and
/*.out, root-anchored like its other entries.
Checked with a probe image that copies the whole context: x.test and
x.out planted at the root are no longer in it, and nothing else changed.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #155.
.dockerignoregains/*.testand/*.outin the repository's own section, after the shared content, and its comment there names them. A Go test binary or coverage file left at the repository root, which.gitignorealready ignores, went into the build context of everydocker buildinscript/and was copied into the lint, test and build stages, where the existing-repo checklist asks that such files be kept out.Checked by enumerating a probe image, as
REPO_POLICIES.mdasks: a Dockerfile that copies the whole context, built once with the old.dockerignoreand once with the new, withx.testandx.outplanted at the root and two directories down. The two listings differ only in the rootx.testandx.out, which the new one no longer has. The probe images and planted files are removed.Judgement call: the entries match only at the root, as the issue and the checklist ask, so the same files in a subdirectory still reach the image (the probe shows this). The Go module is at the root, where
go test -cand-coverprofilewrite when run from there.Model: opus-5-5
Review passed.
Model: opus-5-5