From 48c882a92937480078727a57c122e622924bfc74 Mon Sep 17 00:00:00 2001 From: Noah Robison-Cox Date: Thu, 26 May 2016 18:08:37 -0400 Subject: [PATCH] docs: add explanation of --no-verify to readme --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index a4bbe9d98..35ef57455 100644 --- a/README.md +++ b/README.md @@ -94,6 +94,17 @@ As long as your git commit messages are conventional and accurate, you no longer After you cut a release, you can push the new git tag and `npm publish` (or `npm publish --tag next`) when you're ready. +### Prevent Git Hooks + +If you use git hooks, like pre-commit, to test your code before committing, you can prevent hooks from being verified during the commit step by passing the `--no-verify` option: + +```sh +# npm run script +npm run release -- --no-verify +# or global bin +standard-version --no-verify +``` + ### CLI Help ```sh