New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git hook core.hooksPath #613
Comments
Hi, love the tool too. It seems that a popular hooks manager husky starts to use It would be nice if GitUp follow this config, otherwise users have to choose between these two tools, :(. FYI, there is the official documentation about |
When core.hooksPath is set, use it as hooks path. Resolves #613.
@lucasderraugh sorry to beat a dead horse but based on the change log of the latest release this should now be out correct? problem is i dont see it having any effect/ i cant seem to find an option to enable? im happy to raise a new issue, but figured i would double check there isnt a magic flag to get it rolling |
Which commit hook are you intend to trigger? I think GitUp doesn't support all hooks currently. (I suppose they are cf.) https://github.com/git-up/GitUp/search?q=runHookWithName |
@maku693 pre-commit, commit-msg is what im after. ah opps... i thought i had added them to my repo root turns out i had them in a sorry >< ill post again with the outcome i end up with to help anyone else :) thanks for the reply @maku693 :) |
Thanks @maku693! |
sorry just to confirm say i have Are there any like logs i could look over to see this? (via terminal git commit uses the ~/.githooks fine so i dont think its the hooks themselves right?) |
Hey there love the tool,
i apply my hooks via my .gitconfig via "core.hooksPath" instead of per repository .git folder.
is there anyway of having gitup use the global .gitconfig to gain access to my common hooks?
to avoid having to boostrap every repo
thanks!
The text was updated successfully, but these errors were encountered: