Add .editorconfig and the standard .golangci.yml #59
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
vaultik is missing
.editorconfigand.golangci.yml, diverging from our standard Go repo config.Definition of done
.editorconfigmatching our other Go repos (e.g.sneak/dnswatcher)..golangci.ymlmatching the org-standard config (byte-identical tosneak/dnswatcher's).make checkanddocker build .are green under the new config. If adding the linter surfaces findings, remediate them BEHAVIOR-PRESERVINGLY. If the remediation is large (more than ~50 findings), STOP and report so the lint cleanup can be split into its own issue/PR rather than bundled here.The finishing commit's title must end with
(closes #N)referencing this issue.Update after attempting this: the two files add trivially (both fetched byte-for-byte from
sneak/dnswatcher), but enabling the org-standard.golangci.yml(linters: default: all) surfaces ~2,990 lint findings across 40+ linters on vaultik (wsl1050,nlreturn378,noinlineerr373,revive143,paralleltest138,gosec73, and many more). That is far beyond a behavior-preserving overnight cleanup and needs real judgment (per-finding//nolintvs refactor, or tuning which linters the shared config disables). So.editorconfigand.golangci.ymlare effectively coupled to a large lint cleanup and can't land green together as a small change.Proposed split:
.editorconfignow as a small standalone PR (independent and safe)..golangci.ymladoption plus the lint cleanup is a separate, larger tracked effort — your call whether to do the full behavior-preserving cleanup, or tune the shared.golangci.ymlto something less brutal for existing code. Assigning to you for that decision.Side note: golangci-lint 2.12 flags
gomodguardas deprecated in the shared config — a separate org-wide freshness nit worth a follow-up.