save_config_on_file_change does indeed restore previous behaviour and that more or less solves #2864, which is now closed. But there is more that can be done to support use cases we've been discussing while not impairing any of the existing ones - implementing soft write-locking support for example or just respecting the read-only file permission and not complain at all (or at least making that configurable).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.