CodeQL is missing an inline mechanism to suppress warnings
未关闭
question
- 主要语言
- CodeQL
- 星标
- 10.1k
- 派生
- 2.1k
- 平均合并
- 2 天 15 小时
- 30 天内合并 PR
- 141
描述
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.
贡献指南
评估
这个 Issue 还没有评估数据。