CodeQL is missing an inline mechanism to suppress warnings
Aberta
question
- Linguagem predominante
- CodeQL
- Estrelas
- 10.1k
- Forks
- 2.1k
- Merge médio
- 2d 15h
- PRs com merge (30d)
- 141
Descrição
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.
Guia de contribuição
Avaliação
Esta issue ainda não foi avaliada.