Currently, when you run freight init, we overwrite all supported Git hooks, which can be fairly intrusive. To make this safer by default, freight should automatically back up the entire .git/hooks directory before writing its own hooks—unless the user explicitly opts out.
This approach also opens the door for implementing a rollback or uninstall command, allowing users to restore their original Git hook configuration if needed.
Currently, when you run
freight init, we overwrite all supported Git hooks, which can be fairly intrusive. To make this safer by default, freight should automatically back up the entire .git/hooks directory before writing its own hooks—unless the user explicitly opts out.This approach also opens the door for implementing a
rollbackoruninstallcommand, allowing users to restore their original Git hook configuration if needed.