This repository is configured with git hooks. These hooks run automated code-quality checks like unit tests and linters.
By default, git checks .git/hooks for existing hooks. This repository hosts hooks
in a different location so they can be version controlled. Update your local
configuration, otherwise the hooks won't run. Configure git to use these hooks by running
git config core.hooksPath .git-hooks.
A hook is triggered when its corresponding event takes place. For example, the "pre-commit" hook is triggered when a user initializes a commit. This happens before the commit is created in the git history.
You can add hooks to the .git-hooks folder. For a list of valid hooks, see https://git-scm.com/docs/githooks.
This hook will always run the metadata check. After the metadata check is passed, the hook looks
in each child directory (non-recursive) for the following path: hook_scripts/pre-commit.sh.
If the file is found and it's executable, it will be run. The javascriptv3 script will be run on commit if changes were made in the javascriptv3 directory.
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0