I figured setting some basic hooks for new repositories would be nice to prevent bad habits specific to my workflow while letting CI cover the more project specific conditions, but perhaps my current setup for hooks is not ideal...
Templates are copied during manual clones and apparently every time neovim and lazy clone a plugin.
It's best we only set these hooks for personal repositories if at all.
In addition to the primary issue, hooks are not very cross-platform unless you ensure something like python is installed on all the necessary systems, since writing them in Bash or PowerShell make them more platform specific.
- Remove the templates field and forgo using default hooks.
- Set templates conditionally as some pattern referencing the
~/Projects directory.
- If kept? Ensure all hooks are converted to a cross-platform language
I figured setting some basic hooks for new repositories would be nice to prevent bad habits specific to my workflow while letting CI cover the more project specific conditions, but perhaps my current setup for hooks is not ideal...
Templates are copied during manual clones and apparently every time neovim and lazy clone a plugin.
It's best we only set these hooks for personal repositories if at all.
In addition to the primary issue, hooks are not very cross-platform unless you ensure something like python is installed on all the necessary systems, since writing them in Bash or PowerShell make them more platform specific.
~/Projectsdirectory.