You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The prepare-commit-msg script is only taken into account if it is located in the default location .git/hooks/
However, a common pattern for projects to enforce commit message consistency is to commit a hooks directory such as lib/git/hooks to the project repo and then include the following somewhere in the clone instructions, a Rake task or similar:
git config core.hooksPath lib/git/hooks
This setting is apparently ignored by fork.
How about a quick git config get core.hooksPath instead of hardcoding the default path?
(This is somewhat related to #1749 and maybe #1789 in the sense that Fork should ideally use hook scripts the same way as the git CLI does to prevent surprising behavior.)
The text was updated successfully, but these errors were encountered:
The
prepare-commit-msg
script is only taken into account if it is located in the default location.git/hooks/
However, a common pattern for projects to enforce commit message consistency is to commit a hooks directory such as
lib/git/hooks
to the project repo and then include the following somewhere in the clone instructions, a Rake task or similar:This setting is apparently ignored by fork.
How about a quick
git config get core.hooksPath
instead of hardcoding the default path?(This is somewhat related to #1749 and maybe #1789 in the sense that Fork should ideally use hook scripts the same way as the git CLI does to prevent surprising behavior.)
The text was updated successfully, but these errors were encountered: