You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Code Quality] Add mapclearloop linter to CI enforcement in .github/workflows/cgo.yml #46437
The mapclearloop linter (analyzer #50 in cmd/linters/main.go) is production-ready: type-resolved detection, shadow-safe + comment-safe autofix, and analysistest.RunWithSuggestedFixes golden verification. There are zero production violations in the repo.
However, its sibling mapdeletecheck is CI-enforced while mapclearloop appears nowhere in .github/workflows/cgo.yml.
Suggested Changes
Add -mapclearloop to LINTER_FLAGS strings in .github/workflows/cgo.yml next to -mapdeletecheck.
There are two gate blocks to update (prod gate line ~1208 and wasm gate ~1211).
Files Affected
.github/workflows/cgo.yml (lines ~1208, ~1211) — LINTER_FLAGS prod and wasm gates
Activity
github-actions commentedon Jul 19, 2026
This issue was automatically closed because it expired on 2026-07-19T13:18:16.704Z.