Closed bcoe closed 7 years ago
when we land pull requests, we just need to make sure we use:
feat: description of the new feature I've added fix: description of the bug I've fixed
feat: description of the new feature I've added
fix: description of the bug I've fixed
fix: description of fix BREAKING CHANGE: this is a breaking API change because of reason's x, y, and z.
If we do this, when new versions of marky-markdown are released, we simply need to run:
npm run release and version bump and CHANGELOG will automatically be generated.
npm run release
when we land pull requests, we just need to make sure we use:
feat: description of the new feature I've added
fix: description of the bug I've fixed
If we do this, when new versions of marky-markdown are released, we simply need to run:
npm run release
and version bump and CHANGELOG will automatically be generated.