chore(lint): enable errcheck and staticcheck#1774
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 35 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe change enables ChangesLint configuration and cleanup
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report for CI Build 29912781046Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage remained the same at 46.275%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Turn on errcheck in golangci and resolve the seventeen findings in test files: blank-assign fixture setup calls without a test handle in scope, and assert the ones that feed expected values or reset shared state. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 39e14f2b-1b9a-4a09-94ea-f5ccff6bfc79
📒 Files selected for processing (5)
.golangci.ymlinternal/api/v1beta1connect/authenticate_test.gointernal/store/postgres/prospect_repository_test.gopkg/server/webhook_bridge_test.gotest/e2e/regression/authentication_test.go
Keep the golangci-lint default check set and drop the QF checks, which are editor refactoring suggestions. Fix the one outstanding finding. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4c82e65 to
f343052
Compare
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Summary
Enable the
errcheckandstaticchecklinters. All findings were fixed in the preceding PRs; this turns the gates on.Changes
errchecktolinters.enable, plus the seventeen findings that lived in test files:internal/api/v1beta1connect/authenticate_test.go:_ =on 12 JWK fixture calls (notin scope inside the fixture closures);require.NoErroron thejson.Unmarshalthat builds an expected valueinternal/store/postgres/prospect_repository_test.go: assert the between-cases.cleanup()so a failed cleanup stops the suite at the real problempkg/server/webhook_bridge_test.go:_, _ =on two stub-handler writestest/e2e/regression/authentication_test.go:nolinton the callback server shutdown deferstaticchecktolinters.enablewith the golangci-lint default check set spelled out, minus the QF family (editor refactoring suggestions, not problems)billing/checkout/service.go: drop an inferable type from a var declaration — the one outstanding staticcheck findingTest Plan
golangci-lint runwith both linters enabled and issue caps disabled reports zero findings