CodeQL is missing an inline mechanism to suppress warnings
Aperta
question
- Lingua principale
- CodeQL
- Stelle
- 10.1k
- Fork
- 2.1k
- Merge medio
- 2g 15h
- PR unite (30g)
- 141
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.