Re: Please discuss: what "git push" should do when you do not say what to push?

Martin Langhoff [off-list ref] writes:

--force should change behaviour, immediately, to "current" or even none
(forcing the user to name the remote and branch explicitly).

Any "immediately" change is never going to happen merely based on "I
cannot imagine in what use case it is useful".

As many people already said in the discussion before the RFD message that
is at the root of this thread, the name of the option --force alone
already signals it is something you use after thinking twice.