Supress validation for a line/file #123
Description
Is your feature request related to a problem? Please describe.
On some workflows, the linter will mark things as potential issues because of the way it was written. however, as a writer you have additional information and can possibly conclude that there is no problem. In that situation, having a linter warning is mildly annoying.
For example, I have a workflow that dynamically gets the name of a secret and the accesses secrets[that value]. Linter tell me that the context access might be invalid. this is correct, but I know that the only possible values should be valid or I've done something wrong elsewhere.
Describe the solution you'd like
I'd like to have something along the lines of #pylint: disable etc. for this extension, whether it be a comment ( similar to pylint or eslint ), a config file (e.g. for file x ignore y), an extension setting (ignore warnings of type/ ignore files). To suppress warnings that you know are invalid, to help reduce false positives for issues that the extension simply lacks context for, or to purge warnings that come from bugs of third party workflow authors.
Additional context
related: #59
Activity
felipesu19 commentedon May 18, 2023
#196
jasperfirecai2 commentedon May 18, 2023
While my use case is not the same as that of the other issue, the solution to both can be one and the same. A comment can be file-wide and a config file can be file or project wide. Read the 'describe the solution you'd like'
cringdahl commentedon Nov 3, 2023
This would be especially useful for something like octokit/request-action, which takes arbitrary input keys, but kicks out errors for every one of them.
austinibele commentedon Jul 7, 2025
Bump. This would be very helpful.
MatthieuBizien commentedon Sep 17, 2025
I had to disable the extension because of this, otherwise I have false positives due to problems in .venv.
Official VSCode response: "I think the right and efficient approach is to extensions provide options to exclude." microsoft/vscode#22289 from @sandy081
alexkli commentedon Oct 17, 2025
@MatthieuBizien Agree here:
node_modules, regardless of language/linter/extension. Too bad VS code team doesn't see this the same way :-(.gitignore, on by default, so I don't have to configure the same folders many times. 🙏A polluted problems view filled with false positives that never go away (!) is just going to be useless since you'll be trained to ignore it.
aauren commentedon Dec 28, 2025
Sad that this has gone on for so long without any update. This is pretty basic for almost any linter / language server.
chore: hide release.yml from Problems panel via problems.exclude