On 5 July 2017 at 09:43, Junio C Hamano <gitster@xxxxxxxxx> wrote: > On Tue, Jul 4, 2017 at 11:34 PM, Francesco Mazzoli <f@xxxxxxxx> wrote: >> >> Could you clarify the danger you're referring to? E.g. give an example >> of surprising --force-with-lease behavior that we do not want to >> encourage? > > https://public-inbox.org/git/1491617750.2149.10.camel@xxxxxxxxxxxxxxxxx/ Thanks for clarifying, I had not encountered this because of my git workflow. I'd also be happy with a config item that simply disables `--force` and suggests `--force-with-lease`, but then we'd need a flag to override that config item when the user definitely wants to force push. So we would have something like * `push.disableForce`: config flag that disables `--force` and suggests `--force-with-lease` instead; * `--disable-force` and `--no-disable-force`, config flags to tune the above config parameter at will. What do you think? Thanks, Francesco
