-
Notifications
You must be signed in to change notification settings - Fork 400
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
fix(husky): fix husky release #297
Conversation
Benchmark resultsBase commit: lwc-engine-benchmark
|
@@ -21,15 +21,21 @@ | |||
"release:internalbeta": "yarn prepare && lerna publish --canary=beta --skip-git --yes --registry='https://nexus.soma.salesforce.com/nexus/content/repositories/npmjs-internal/'", | |||
"changelog": "yarn changelog:generate && yarn changelog:publish", | |||
"changelog:generate": "conventional-changelog -p angular -i CHANGELOG.md -s -r 0", | |||
"changelog:publish": "git add CHANGELOG.md && git commit -m 'docs(changelog): publish release changelog' && git push", | |||
"commitmsg": "validate-commit-msg" |
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.
How was this script getting triggered before?
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.
with an old husky interface, by specifying 'commitmsg' you tell husky to intercept commit message - automagic. With a new version of husky they explicitly make you create 'husky' object in your packages.json
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.
LGTM
Details
Use commitlint instead of validate-msg library. Fixes #171
Does this PR introduce a breaking change?