Adding Husky and Commitlint #550
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
see .gitignore ci: removing git add ci: using lint-staged since it only works staged files ci: adding a pre-commit with npx lint-staged ci: improve flow with husky and commitlint ci(ci-improve): 👷 testing the working of commitlint commitlint checks with husky invalid commit message test test
poppyseedDev
force-pushed
the
commitlint
branch
from
66a99b0
to
7bc845b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed my pull requests a lot of times weren't passing the following checks:
npm run prettier:checkcommitlinton PRTherefore I decided to add husky to automatically enforce these rules on every commit.