标签：
Because semantic-release requires a specific message format, it‘s easier to follow this convention using a tool called commitizen. In this lesson, we‘ll use it to write our first conventional commit message.
Install:
npm i -D commitizen cz-conventional-changelog
package.json:
{ "czConfig": { "path": "node_modules/cz-conventional-changelog" }, "scripts": { "commit": "git-cz", "start": "cross-env NODE_ENV=development webpack-dev-server --progress --profile --colors --display-error-details --display-cached --inline", "test": "cross-env NODE_ENV=test karma start", "test:single": "cross-env NODE_ENV=test karma start --single-run", "semantic-release": "semantic-release pre && npm publish && semantic-release post" }, }
The convention it follows is from angular
n this lesson, we‘ll add a new feature to our library and use commitizen to generate our commit message that follows the convention for semantic-release to know it needs to bump the minor version.
npm run commit
It will let you go thoguht few steps of commit message, then you can push to github.
Now that we have everything set up with semantic-release and we have a feature commit, let‘s push that up and watch TravisCI use semantic-release do our library release automatically.
After you git push to master. Traavis will automatically run the build and tests, if everything pass, then it will automaticlly update the package version number and release the package in github and npm.
[Javascript] Writing conventional commits with commitizen
标签：
原文地址：http://www.cnblogs.com/Answer1215/p/5488064.html
