gregdeane/steps-to-autogenerate-changelog.md

Created February 4, 2016 13:57

Star (0) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/gregdeane/424657bc67b5185388e4.js"></script>
Save gregdeane/424657bc67b5185388e4 to your computer and use it in GitHub Desktop.

Download ZIP

Steps to auto-generate changelog

Raw

steps-to-autogenerate-changelog.md

Make changes
Commit those changes
Make sure Travis turns green
Bump version in package.json
conventionalChangelog
Commit package.json and CHANGELOG.md files
Tag
Push

The reason why commit and tag should be run after conventionalChangelog is that the CHANGELOG should be included in the new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment