Feature request: overwrite existing database, but ask first
- 主要語言
- CodeQL
- 星號
- 10.1k
- 分支
- 2.1k
- 平均合併
- 2 天 15 小時
- 30 天內合併 PR
- 141
描述
I'm auditing a customer application. Their build system has never been set up for CodeQL, so there's a lot of tweaking and setup that has to be figured out to get it all working. Naturally, as part of this process, I'm running `codeql database create [...] --overwrite` a bunch of times as I iterate through all the build issues to fix stuff.
Finally, in a joyous moment, the build _actually runs!_
I wait 25 minutes for it to build, get the success report, then excitedly hit up a couple of times in my terminal to run my last `codeql database analyze` command. But I'm a clumsy oaf, and in all the excitement I accidentally run the `codeql database create [...] --overwrite` command again. WHAM. Whole database gone. I resign myself to waiting another 25 minutes for the build to complete and go stare into the void for a while.
Please save me from myself by adding an `--overwrite=ask` option (or similar) that prints a warning and requires me to write something like "yes" before doing the overwrite. Thanks.
貢獻指南
研究方向
Start with the `codeql database create` command and its existing `--overwrite` behavior. Determine how an interactive confirmation option should be exposed and verify that an overwrite warning blocks the operation until confirmation is provided.
由索引模型根據 Issue 內容生成。
評估
- 領域
- cli, devtools
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100