-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create changelog #74
Comments
I've been looking into Conventional Commits as a lot of the big boys (angular, aurelia, ng-bootstrap, etc) are using it as a system to automatically generate a changelog and bump their package version. By using this approach via Standard Version our release process could be as follows:
And we'd be done, that would auto-generate a changelog, bump the version number, and publish to npm/push to git. It's well worth a read and I'd be up for trying it out. Commit messages on branches can still be whatever we like, as long as when the branch is merged it gets squashed into a single commit that is conventional, and any commits to master should be conventional. |
Also, I've thought about creating new |
Yes gitflow works for me, master essentially being the production branch. |
* chore(changelog): added changelog process (#79) Fixes #74 * chore(build): fix build getting stuck * fix(dependencies): add http module to imports Fixes #80 * fix(input): fixed extensions not working when not specified (#83) fixes #82 * fix(output): emit onRemove when all files are cleared (#85) fixes #84
Must be done before v1.0.0
The text was updated successfully, but these errors were encountered: