Sharing hooks with the team (husky) in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Husky in the context of Git?

Husky is a tool that helps you run scripts automatically before Git actions like commit or push. It makes sure everyone on the team runs the same checks.

beginner

How does Husky help share Git hooks with a team?

Husky stores hook scripts in the project configuration, so when team members clone the repo and install dependencies, the hooks are set up automatically on their machines.

intermediate

Where do you define Husky hooks in a project?

You define Husky hooks in the package.json file under the "husky" section or in separate hook files managed by Husky in the .husky directory.

beginner

What command do you run to install Husky hooks after cloning a repo?

You run `npm install` or `yarn install` to install dependencies, and Husky will automatically set up the Git hooks defined in the project.

beginner

Why is sharing Git hooks with Husky better than manually setting hooks?

Because Husky automates hook setup, it avoids mistakes and ensures all team members use the same checks without extra manual steps.

What does Husky primarily help with in Git?

A Running scripts automatically before Git actions

B Merging branches automatically

C Creating new Git repositories

D Backing up Git data

Husky runs scripts automatically before Git actions like commit or push to enforce checks.

Where are Husky hooks usually defined?

A In the package.json or .husky directory

B In the .gitignore file

C In the README.md file

D In the node_modules folder

Husky hooks are defined in package.json under "husky" or in the .husky directory.

How do team members get Husky hooks after cloning a repo?

A By manually copying hook files

B By running npm install or yarn install

C By running git init

D By creating hooks themselves

Running npm install or yarn install installs dependencies and sets up Husky hooks automatically.

Which Git action can Husky run scripts before?

A branch

B clone

C fetch

D commit

Husky commonly runs scripts before commit or push actions.

What is a key benefit of using Husky for Git hooks?

A Automatically merges conflicts

B Increases Git repository size

C Ensures consistent hooks for all team members

D Removes the need for Git

Husky ensures all team members have the same Git hooks set up automatically.

Explain how Husky helps share Git hooks with your team.

Think about how Husky makes sure everyone runs the same checks without manual setup.

Describe the steps a team member takes to get Husky hooks after cloning a repository.

Focus on what happens after cloning and installing dependencies.