github / github/codeql

Feature request: overwrite existing database, but ask first

Aperta
#19,909 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
CodeQL
Stelle
10.1k
Fork
2.1k
Merge medio
2g 15h
PR unite (30g)
141

Descrizione

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.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Ambito
cli, devtools
Tipo di issue
Funzionalità
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.