-
Notifications
You must be signed in to change notification settings - Fork 661
fix: added commitlint rules #870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #870 +/- ##
=======================================
Coverage 89.92% 89.92%
=======================================
Files 21 21
Lines 3494 3494
Branches 298 298
=======================================
Hits 3142 3142
Misses 346 346
Partials 6 6Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good! Just have one question, doesn't necessarily need changing
| "always", | ||
| "lower-case" | ||
| ], | ||
| "subject-case": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's your reasoning here? I feel like we want it to be always lower case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realizing that this probably looks word by word, it makes sense to allow other cases to include variable names in commit messages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
|
🎉 This PR is included in version 4.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
commitlintrules. Resolves Include commitlint.config.js in repo #867npm auditreview.Checklist
npm testpasses (tip:npm run autofixcan correct most style issues)