On Thu, Apr 11, 2024 at 1:34 PM Kipras Melnikovas <kipras@xxxxxxxxxx> wrote: > > > If this is mostly about saving typing, you could get a similar effect adding > > an alias. Something like > > > > git config --global alias.pushfl 'push --force-with-lease' > > Correct, and I already have an alias: > 'pf = push --force-with-lease --force-if-includes'. > > However, I see the config option more valuable - it would protect against > accidental `push -f`, which, out of habit, is very probable to run on accident. > With the config option, would feel safe and wouldn't need the alias either. It would normalize the use of `push -f` in people's muscle memory, which would be a potential disaster if someone lost their configuration, but not this muscle memory. It also would break automation/scripts - `git push` is likely used by both humans and automation (custom one-off automation like a personal script, or automation shared by many people) - if they're expecting `git push -f` to do the legacy behavior, then it'll break things if the meaning of `-f` changes. A separate flag (or just using an alias if it's for saving typing) would be safer. > > Thanks. > >
