You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project doesn't have git hooks which can trigger automatically on committing or any git commands . Git Hooks can help us to automate the process like linting , running some tests before pushing to GitHub , etc .
Use Case
We can have a pre-commit hook which can trigger automatically linting to lint the changed files before we commit .
Possible Solution
One of the possible and most famous solution I can think of is using Husky . It's easy to setup .
Context
It can automate the process of linting & testing on every commit .
Detailed Description
We can use Husky package to setup the Git Hooks . I found out easy to setup & use with mono-repos . We just need to install the Husky package & setup the husky command in package.json file and we have setuped the Git Hooks .
The text was updated successfully, but these errors were encountered:
@Krish-bhardwaj . Sorry but I have opened this issue for myself . I am waiting for someone from core team to give their views on it. You may look for issues in the repo
Feature Request 🛍️
The project doesn't have git hooks which can trigger automatically on committing or any git commands . Git Hooks can help us to automate the process like linting , running some tests before pushing to GitHub , etc .
Use Case
We can have a
pre-commit
hook which can trigger automatically linting to lint the changed files before we commit .Possible Solution
One of the possible and most famous solution I can think of is using
Husky
. It's easy to setup .Context
It can automate the process of linting & testing on every commit .
Detailed Description
We can use
Husky
package to setup the Git Hooks . I found out easy to setup & use with mono-repos . We just need to install the Husky package & setup the husky command inpackage.json
file and we have setuped the Git Hooks .The text was updated successfully, but these errors were encountered: