-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add changelog generation and commit message convention #30
Comments
ref: ipfs/community#145 |
Semantic Release (wonderful utility for automatic package publishing) is using the Angular convention, worth looking into: https://github.com/semantic-release/semantic-release#default-commit-message-format |
@victorbjelkholm also look at the last link in the original issue, standard-version does something similar as far as I understand |
Nvm semantic-release is much more comprehensive, need to look at that, could be super nice for us |
@dignifiedquire ah, that's true. standard-version mentions semantic-release over here: https://github.com/conventional-changelog/standard-version#how-is-standard-version-different-from-semantic-release Seems like standard-version does a subset of what semantic-release does (like pushing and publishing) |
This is a rough draft of things I suggest to adapt, for making the release process as automated as possible while generating high quality releases.
Steps for new
|
Todos:
|
First version is released in 7.0.0 |
What do we need to do to finish this one? Let's review it during the next sprint call (//cc @RichardLitt @flyingzumwalt) |
This is done, right? |
@diasdavid still don't have commit validation on CI |
I don't think commit validation on CI is particularly great, we can use the |
Examples of projects using strict commit message conventions to auto generate changelogs
Possible commit message conventions
Eco system in npm land
The text was updated successfully, but these errors were encountered: