chore: add lint-staged and Husky
#105
Merged
Conversation
This file contains hidden or 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
12 tasks
Pull Request Test Coverage Report for Build 11755886309Details
💛 - Coveralls |
rolandjitsu
reviewed
Nov 8, 2024
rolandjitsu
reviewed
Nov 8, 2024
Signed-off-by: Jon Koops <jonkoops@gmail.com>
Collaborator
Author
|
This one is ready to be reviewed, can I ask you for another pass @rolandjitsu? |
rolandjitsu
approved these changes
Nov 9, 2024
Collaborator
Author
|
Thanks again! |
|
🎉 This PR is included in version 3.0.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Adds
lint-stagedand Husky to automatically fix linting and formatting issues on commit. This helps prevent issues from slipping in and keeps the code consistent between contributions.Does this PR introduce a breaking change?
No.
Other information
Not relevant.