On CLI I figure out the script once.

Put it in a script.

Cron it if I want it to be daemonized.

Never think about it ever again.

Anti-CLI folks just have a bad workflow.

They see the script as the end, when in reality it’s a foundation. I rarely look at my foundation. I build on it.

With this workflow I have dozens, hundreds, or thousand of automatic actions that “just work”. Idk, works for me.

That said, if you prefer to click yourself to RSI to accomplish the same task, who am I to judge. I just watch and nod until I’m asked for a suggestion.

True, in the situation with a local history maybe it’s worthwhile to --force to nuke an empty remote. In that case it is practical to do so. I just typically like to find non-force options.

There are multiple solutions to this without using --force.

Move the files, clone, unmove the files, commit, push being the most straightforward that I can summon at this time… but I’ve solved this dozens of times and have never use --force.