Description
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.