-
Notifications
You must be signed in to change notification settings - Fork 65
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
Suggestion - Documentation & new option around commit hook #500
Comments
Clearly, it isn't actually disabled. Husky does provide configuration to disable it properly: We won't be adding extra configuration options to handle this situation, but would accept PRs to update our docs and point to those husky details |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10.0.1
v18.18.2
We're using this plugin which is awesome. Recently we got an error when running
semantic-release
in our pipeline that took us a while to figure out.We are using Husky, but that's disabled in the pipeline. There was a log at the bottom regarding our unit tests which I thought was a result of the job failing. This was an incorrect assumption. It was because our unit tests were being run due to the plugin and there was missing a build file. I was unaware until I looked at the source code that this plugin would run our git commit hook (which now feels obvious). Before putting in a PR I wanted to open a ticket with my suggestions;
README.md
so its clear if you have a git commit hook it will be ran--no-verify
flag to the commit functionI'm unsure how to do the 3rd option but something like the below I feel would work.
The text was updated successfully, but these errors were encountered: