Operationalising Golangci-lint
summary
Shows concrete bug catches: pointer misuse with errors.As, url.Query returning a copy, and missing rows.Err() that hides deadline/cancel errors. Demonstrates running golangci-lint with linters like staticcheck to find these issues, and using a Google sheet that generates config (sheet last updated for v1.61) to tune which checks to enable. Notes there are more than 100 linters with 40+ duplicated checks and recommends using golangci-lint’s new-from-rev flag to roll fixes in gradually.
AI-written summary · about
chapters (6)
- 0:00Introduction to linters
- 3:13Linters catch tricky bugs
- 9:19Why use golangci-lint
- 13:57Configuring golangci-lint
- 16:46Fixing issues iteratively
- 19:35Q&A session
related talks
29mThe Joy of Linters: Good Engineering Practices & Productivity Boosters
28m"Common tips & mistakes" in Go — and How to Fix Them
19mMake Linting Great Again
25mExploring Some Essential Security Checks for Any Open Source Go Project
26mUsing and Writing Go Analyses
07mMake Linting Great Again
32mWriting a Static Analyzer for Go Code
23mAnalysis and Transformation Tools for Go Codebase Modernization