Full support for other conventional-changelog-* presets
See original GitHub issuePerhaps it’s not a matter of commitlint. But since it’s a problem with commitlint, I set up an issue here.
Expected Behavior
I want to commit using commitizen and pass commitlint through hook (Hook by husky ‘commitmsg’).
Current Behavior
yarn run v1.3.2
$ git-cz
cz-cli@2.9.6, cz-conventional-changelog-atom@0.0.2
Line 1 will be cropped at 72 characters. All other lines will be wrapped after 72 characters.
? Select the type of change that you're committing: 💚: when fixing the CI build
? Write a short, present-imperative tense description of the change:
test
? Provide a longer description of the change:
A combination of "commitzen" and "conventional-changelog-atom". And check "commit" with "commitlint".
? List any breaking changes or issues closed by this change:
husky > npm run -s commitmsg (node v9.5.0)
⧗ input: 💚 test
✖ message may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
Affected packages
- cli
- core
- prompt
- config-angular
Steps to Reproduce (for bugs)
- Run commitizen by
yarn cz
- Enter the commitizen prompt.
- Auto run husky hook
- Occur error
package.json
{
"scripts": {
"commitmsg": "commitlint -e $GIT_PARAMS",
"cz": "git-cz"
},
"config": {
"commitizen": {
"path": "cz-conventional-changelog-atom"
}
},
"commitlint": {
"extends": [
"@commitlint/config-conventional"
],
"parserPreset": "conventional-changelog-atom"
}
}
Context
I don’t know the cause. I’m sorry if there is a problem with the conventional-changelog-atom
module. Or is there something missing in commitlint’s parser-opts? Is there anything else need?
Your Environment
Executable | Version |
---|---|
commitlint --version |
6.1.2 |
“conventional-changelog-atom” | “^0.2.3” |
“cz-conventional-changelog-atom” | “^0.0.2” |
“husky” | “^0.14.3” |
git --version |
2.15.0 |
node --version |
v9.5.0 |
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
conventional-changelog-conventionalcommits - npm package
Visit Snyk Advisor to see a full health score report for conventional-changelog-conventionalcommits, including popularity, security, maintenance & community ...
Read more >conventional-changelog-beemo - npm
Conventional changelog preset for Beemo and associated projects.. Latest version: 3.0.1, last published: 6 months ago.
Read more >conventional-changelog-cli/README.md - UNPKG
The CDN for conventional-changelog-cli. ... **Note: `config` here can work with `preset`, which is different than `options.config` ... Only support GitHub.
Read more >conventional-changelog-conventionalcommits | Yarn - Yarn
Indirect Usage (as preset). Use the Conventional Changelog CLI Quick Start with the -p conventionalcommits option.
Read more >Conventional Commits
Conventional Commits. A specification for adding human and machine readable meaning to commit messages. Quick Summary Full Specification Contribute ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Would be really nice if commitlint supported plugins, eslint style. Then someone could write, for example, and “emoji” rule plugin.
Closing this because plugins are supported: https://commitlint.js.org/#/reference-plugins