chore: migrate nvsnap and nvcf-unbound golangci-lint configs to v2#228
Conversation
|
Warning Review limit reached
Next review available in: 23 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: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughBoth Go services migrate their golangci-lint configurations to version 2. The changes restructure linter settings, revise enabled linters and exclusions, and configure formatter handling separately. Changesgolangci-lint configuration migration
Estimated code review effort: 3 (Moderate) | ~25 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@mesutoezdil , can you please rebase off of main? It should fix the codeql failures. |
8a621d1 to
ed76048
Compare
|
done, thx |
ed76048 to
3858c76
Compare
Both .golangci.yml files were still in v1 schema (no version field, linters-settings, exclude-dirs, exclude-rules). golangci-lint v2 rejects them outright with "unsupported version of the configuration", so linting has not been running for either module. Migrated both with the official `golangci-lint migrate` command, then hand-restored the explanatory comments it drops, in particular the gosec exclude rationale in nvsnap (world-readable cache dirs needed for cross-uid pod restore). Verified both configs load with `golangci-lint config verify` and `golangci-lint run` now executes instead of failing immediately. nvsnap is Linux-only and does not type-check on this darwin host, so also cross-compiled with GOOS=linux to confirm the lint pass itself runs end to end (358 pre-existing findings surfaced, out of scope for this change). NO-REF Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
3858c76 to
51e0189
Compare
TL;DR
nvsnap and nvcf-unbound .golangci.yml were still v1 schema, so golangci-lint v2 failed to load them. Migrated both with the official migrate tool and restored stripped comments. golangci-lint config verify passes for both.
Issues
NO-REF
Summary by CodeRabbit