From 84aa9eac11634d8fe6053fa7946dee5b77f09581 Mon Sep 17 00:00:00 2001 From: Filip Barakovski Date: Tue, 20 Nov 2018 01:16:39 +0100 Subject: [PATCH 1/2] Changes 'side affects' to 'side effects' (#141) --- hook | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hook b/hook index 28a7f38..1bf23b8 100755 --- a/hook +++ b/hook @@ -38,7 +38,7 @@ elif [[ -x "$LOCAL" ]]; then fi # -# Add --dry-run cli flag support so we can execute this hook without side affects +# Add --dry-run cli flag support so we can execute this hook without side effects # and see if it works in the current environment # if [[ $* == *--dry-run* ]]; then From a84bdc87aabf79493343a366872ab204a62b1613 Mon Sep 17 00:00:00 2001 From: Ace Young <2482343+aceyoung9@users.noreply.github.com> Date: Tue, 4 Jun 2019 06:50:52 -0400 Subject: [PATCH 2/2] Update link to official npm docs (#143) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 137671e..16f6b2e 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ the existing `pre-commit` file in your `.git/hooks` folder. Existing `pre-commit` will try to run your `npm test` command in the root of the git repository by default unless it's the default value that is set by the `npm -init` script. +init` script. But `pre-commit` is not limited to just running your `npm test`'s during the commit hook. It's also capable of running every other script that you've @@ -116,7 +116,7 @@ or as `"pre-commit.{key}` key properties in the `package.json`: It's all the same. Different styles so use what matches your project. To learn more about the scripts, please read the official `npm` documentation: -https://npmjs.org/doc/scripts.html +https://docs.npmjs.com/misc/scripts And to learn more about git hooks read: