github / github/codeql

CodeQL is missing an inline mechanism to suppress warnings

Open
#11,427 31 comments 77 reactions 1 assignee Claimed by @sj View on GitHub
question
Dominant language
CodeQL
Stars
10.1k
Forks
2.1k
Avg merge
2d 15h
Merged PRs (30d)
141

Description

This was asked about in https://github.com/github/codeql/issues/9298 and the issue log stated "closed as not planned". The "answer" was to dismiss via the UI. But this alone is really not a sufficient mechanism:

* Having to interact with the UI is supremely annoying
* Spurious new warnings if the code moves cannot be avoided this way
* It is _good_ to be forced to comment these exception inline where they happen
* What if you are running codeql locally? Then here is _no_ mechanisim?

Please consider supporting this basic, table-stakes feature that many, many linting/scanning tools afford.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.