ci/sonar: scope complexity rules to production code, send the release version #75
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/sonar-scope"
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?
Repo half of #65, part of #73. The first scan of main reported 144 go:S3776 cognitive complexity findings, 94 of them in _test.go files, and 5 of 14 go:S107 parameter-count findings in tests. Table-driven tests are long by design, so sonar-project.properties now ignores both rules on **/*_test.go through sonar.issue.ignore.multicriteria, versioned in the repo instead of the server UI. The CI scan also passes sonar.projectVersion taken from the last wraptool-v tag, falling back to 0.0.0, so the server-side new-code definition Previous version resets at each release instead of never. Server half already done by the operator: Go quality profile extended with the S3776 threshold at 25, and the project on the built-in Sonar way gate with new-code conditions only. Effect is visible on the first main scan after merge. 🤖 Generated with Claude Code