tracking: SonarQube cleanup after the first scan of main #73
Loading…
Reference in a new issue
No description provided.
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?
Baseline from the first CI scan of main on 2026-10-19, run 393: 22677 lines of code, 209 issues of which 167 critical, 34 major, 5 minor and 3 info, 14 bugs, 1 vulnerability, 0 hotspots, coverage 79.2 percent, duplication 1.0 percent, quality gate OK. Per-rule split: go:S3776 cognitive complexity 144 with 94 in tests, go:S1192 duplicated literals 22, go:S107 too many parameters 14, Web:InputWithoutLabelCheck 14, Web:S5255 4, javascript rules 6, go:S1135 TODO 3, go:S1871 1, go:S1186 1. Work items in order: 65 sonar config and quality gate, then the mechanical PRs 66 webui literals, 67 doctor literals, 68 template accessibility, 69 seed_cache_index.js, then 70 parameter counts and 71 complexity refactors one package per PR. Small fry handled inline in whichever PR touches the file: go:S1871 duplicate branch in internal/doctor/render_human.go, go:S1186 empty function comment in cmd/platform_windows.go, and the three go:S1135 TODO comments in cmd/up.go are accepted as is. Related but not Sonar: 72 doctor env_files parsing. Findings are readable from the agent through the sonar MCP tools proxied by wraptool. PR analysis is not available on Community Build, so each fix is verified by the main scan after merge.
closed