On Tue, Feb 20, 2024, at 04:59, Ricardo C wrote: > That makes sense. Do you have any ideas on how to address this? It feels to me > like providing this config option is fundamentally incompatible with requiring > backwards-compatible behavior regardless of configuration. If my armchair also had a time machine: one could have used an `-s` option to `git` (`git -s stash`) that only reads a few configuration variables, like `user.name` and `user.email`. It would read none of the variables meant for making interactive/custom use convenient. This would be meant for scripts. That way new user-convenience config variables wouldn’t interfere with some `git -s` invocation deep in some script somewhere. As for the status quo though one seems stuck.
