Skip to content

fix: emit an error when no linters enabled#6323

Merged
ldez merged 2 commits intogolangci:mainfrom
ldez:fix/impossible-cases
Jan 15, 2026
Merged

fix: emit an error when no linters enabled#6323
ldez merged 2 commits intogolangci:mainfrom
ldez:fix/impossible-cases

Conversation

@ldez
Copy link
Copy Markdown
Member

@ldez ldez commented Jan 15, 2026

I tested the following cases:

  • default: none + enable with an explicit empty slice -> error
  • default: none + enable with an explicit empty slice + formatters -> no error
  • default: all + disable all linters -> error
  • default: all + disable all linters + formatters -> no error
  • default: standard + disable all linters -> error
  • default: standard + disable all linters + formatters -> no error
  • default: fast + disable all linters -> error
  • default: fast + disable all linters + formatters -> no error

Fixes #6321

@ldez ldez added this to the unreleased milestone Jan 15, 2026
@ldez ldez added the bug Something isn't working label Jan 15, 2026
@ldez ldez force-pushed the fix/impossible-cases branch 2 times, most recently from c87af4c to 2fea5ae Compare January 15, 2026 21:08
@ldez ldez force-pushed the fix/impossible-cases branch from 2fea5ae to c1d22c5 Compare January 15, 2026 21:32
@ldez ldez merged commit 7024fff into golangci:main Jan 15, 2026
18 checks passed
@ldez ldez deleted the fix/impossible-cases branch January 15, 2026 22:59
@ldez ldez modified the milestones: unreleased, v2.9 Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fail when no linters are passed

3 participants