How do you configure a git repository to run code sanity checking tools right before making commits, and preventing them if the test fails?
Answer / Mahendra Pal Gautam
To run code sanity checking tools before making commits in Git, follow these steps:n1. Install the tool(s) on your development machine.n2. Create or update a `pre-commit` hook script to run the tool and exit with an error status if the test fails. Here's an example using a shell script: $ cat .git/hooks/pre-commitn#!/bin/shn# Run your code sanity checking tool here, e.g., eslint or lintn./node_modules/.bin/eslint . --max-warnings=0 || exit 1nSave this script in the `.git/hooks` directory and make it executable: $ chmod +x .git/hooks/pre-commit.n3. If you want to bypass the hook during development, you can add your email address to the `.mailmap` file or use the `--no-verify` option when committing.
| Is This Answer Correct ? | 0 Yes | 0 No |
What are the different ways you can refer to a commit?
How to rebase master in git?
How to resolve a conflict in git?
What is the common branching pattern in GIT?
What is git reflog?
Why GIT better than Subversion?
Name some git commands and also explain their functions?
What is GIT version control?
How to revert previous commit in git?
Tell me the difference between head, working tree and index, in git.
How git instaweb is used?
What is ‘bare repository’ in GIT?