unused-suppression
asitis-disable comment suppresses nothing.
Source: asitis CLI contract: Suppression (github.com), read 14 October 2026.
On GitHub: the rule doc and the tests.
All rules73
What it catches#
asitis-disable comment suppresses nothing.
An asitis-disable-next-line or asitis-disable-file comment (or bare asitis-disable) for a rule that has no finding on the line after the comment, or anywhere in the file for the file form. A comment for a rule that .asitisrc.json turns off for that file is not reported. It is a note: the comment is harmless, but it is now a hidden comment with no purpose.
Why it matters#
The finding it was for is gone, so the comment can go too.
Bad example#
<!-- asitis-disable-next-line duplicate-rule -- release and hotfix paths both list this -->
- Rebase on main before you push.
The duplicate it covered was removed in a later edit. The comment stayed.
Good example#
- Rebase on main before you push.
How to fix#
Delete the comment, or just the rule id in it if the comment names several. If you expected a finding here, check that the comment sits on the line directly above the one it covers: asitis-disable-next-line applies only to the line after the comment closes.
Suppress or configure#
For one finding, put a comment on the line above it. The reason after -- is optional but worth writing:
<!-- asitis-disable-next-line unused-suppression -- why this one is fine -->
For a whole file:
<!-- asitis-disable-file unused-suppression -- why this file is an exception -->
For every file, turn it off or change its severity in .asitisrc.json:
{ "rules": { "unused-suppression": "off" } }
A .asitisrc.json overrides entry limits a change to some paths, and a baseline (asitis lint --format json --write-baseline) accepts today's findings so only new ones fail the build.
Source#
asitis CLI contract: Suppression, read on 14 October 2026.
Related guides
Run the rule
- In your browser, on one file
- In Claude Code, on the project
- In CI, on every pull request
This page is generated from the plugin's rule registry. Edit it on GitHub. False positive? Open an issue with the line it fired on.