Add missing standard config files: .gitignore, .dockerignore, .editorconfig, .golangci.yml #1
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?
bsdaily is missing several standard repo files (verified against
main: the root has no.gitignore,.dockerignore,.editorconfig, or.golangci.yml).Definition of done
.gitignoreand.dockerignore(match a sibling such assneak/dnswatcher)..editorconfigmatching our standard Go repos (copysneak/dnswatcher's)..golangci.ymlbyte-identical tosneak/dnswatcher's (org-standard config).make checkanddocker build .are green under the new config. If 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.Splitting this: I'm landing the three non-lint dotfiles now (
.gitignore,.dockerignore,.editorconfig— all copied fromsneak/dnswatcher,.gitignoreadapted to the/bsdailybinary) as a PR that keepsmake checkgreen. That PR isrefs #1, notcloses, because the.golangci.ymlpart is deferred.Adding the org-standard
.golangci.yml(linters: default: all) surfaces 167 lint findings in bsdaily's existing code (baseline with no config is 0). Breakdown:wsl_v549,noinlineerr43,nlreturn16,lll13,err11312,revive12,gosec9,noctx6, plus complexity linters. That is a substantial behavior-preserving cleanup, not an overnight change. Your call: do the full cleanup, or tune the shared.golangci.ymlto be less brutal for existing code. Assigning to you for that decision; the.golangci.ymladd closes #1 once it lands green.