how do you config hanzo so that it automatically create hook sample

[smitthakkar1]

So I have configured hanzo in my project, it works well. The only problem I am having is whoever clone the git repo needs to run hanzo -i pre_commit -s command in order to generate sample script which points to pre_commit.dart where I have some stuff.

Is there any way I can automate this process and just run hanzo -i pre_commit -s everytime flutter pub get runs. We were using husky in typescript before which was working awesome and does this automation for you.

[ThinkDigitalSoftware]

If you already have a Dart file, then install it without creating the sample. Also, why do you want to run a "pre-commit" file before pub get runs? This is for committing

[smitthakkar1]

Thanks for your instant reply. 😄

I do have dart file but the reason I run hanzo -i pre_commit -s is it will create a file pre-commit under .git/hooks which is referring to pre_commit.dart file and that's how git will know what to run before commit.

Also, why do you want to run a "pre-commit" file before pub get runs? This is for committing

I want to run hanzo -i pre_commit -s every time it runs get packages to make sure when someone clone the repo for the first time/edit .git folder, they have that .git/hooks/pre-commit script.

[ThinkDigitalSoftware]

If you check out the documentation for hanzo,

Option/Flag	abbreviation	description
--add-sample	-s	If flag is passed it will create a sample Dart script. Defaults to false
--install <hook_name>	-i	Creates a bash script for the hook passed. Defaults to pre_commit script. Example: -i pre_commit
--remove <hook_name>	-r	Removes a bash script for the hook passed. Example: -r pre_commit. Defaults to all

-s is for adding a sample. Which means it'll create a file for you in tool/_hook_name._dart with some default text. But if you're already committing this to git, then the file will already exist, making this step pointless. You will have to enable the git hook though, but you can't automate this part unless you write a script and have them download and run the script which clones the repo and adds the hooks. Actual git hooks live in the .git folder, and so do the settings, which is ignored by git. What hanzo does is create the .git hooks file in the .git directory and then makes it call the corresponding dart file. I believe that creating a setup script is the best way to go