--with-danger

--make-it-so

--do-the-thing

--go-nuts

--safety-off

So many fun options.

I find it important to include system information in here as well, so just copy-pasting an invocation from system A to system B does not run.

For example, our database restore script has a parameter `--yes-delete-all-data-in` and it needs to be parametrized with the PostgreSQL cluster name. So a command with `--yes-delete-all-data-in=pg-accounting` works on exactly one system and not on other systems.

I'm a fan of --safety-off. It gives off a 'aim away from face' or 'mishandle me and I'll blow a chunk out of your DB' vibe.

It's in the UI not the command line, but I like Chromium's thisisunsafe

I've done a few --execute --i-know-what-im-doing for some more dangerous scripts

--commit is solid too