CI runs go test (.github/workflows/go.yml) and the README's Development section advertises go test -race ./... — but the repo contains zero test files, so the test step is a no-op and the green check is misleading.
For a 1,200-LOC utility this doesn't need much: a minimal suite around config loading/env switching and output shaping would make the CI signal real. Alternatively, explicitly accept the tool as test-free and drop the test step + README claim so nobody mistakes green CI for coverage.
Found during the 2026-07 CLI stack review (index in environment-setup).
CI runs
go test(.github/workflows/go.yml) and the README's Development section advertisesgo test -race ./...— but the repo contains zero test files, so the test step is a no-op and the green check is misleading.For a 1,200-LOC utility this doesn't need much: a minimal suite around config loading/env switching and output shaping would make the CI signal real. Alternatively, explicitly accept the tool as test-free and drop the test step + README claim so nobody mistakes green CI for coverage.
Found during the 2026-07 CLI stack review (index in environment-setup).