Skip to content

Instantly share code, notes, and snippets.

@gregdeane

gregdeane/steps-to-autogenerate-changelog.md

Created February 4, 2016 13:57
Show Gist options
  • Save gregdeane/424657bc67b5185388e4 to your computer and use it in GitHub Desktop.
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
  1. Make changes
  2. Commit those changes
  3. Make sure Travis turns green
  4. Bump version in package.json
  5. conventionalChangelog
  6. Commit package.json and CHANGELOG.md files
  7. Tag
  8. 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