On Tue, Jan 30, 2024 at 12:49:08AM +0300, Sergey Organov wrote: > > Please don't. I set it to "false", because I find the default behavior a > > pointless roadblock if you are already aware that "git clean" can be > > destructive. Surely I can't be the only one. > > Well, provided there is at least one person who finds it useful to set > it to 'false', I withdraw my suggestion. > > That said, did you consider to: > > $ git config --global alias.cl 'clean -f' > > instead of > > $ git config --global clean.requireForce false > > I wonder? Not really, as when I originally set the config in 2007, it was just undoing the then-recent change to default clean.requireForce to true. I already had muscle memory using "git clean" as it had worked historically from 2005-2007. I know that isn't necessarily relevant for new users today, but my point is mostly that we have clean.requireForce already and people would probably be annoyed if we took it away. :) -Peff
