-
Notifications
You must be signed in to change notification settings - Fork 513
Consider using conventional-changelog to generate changelog #1563
Comments
Sample logs generated based on your commits AlignedObjectValuesAnonymousFunctionExpressionAPI
Autofix
CheckerCLIConfiguration
|
This is pretty great! Thanks for the recommendation @stevemao. I assume we'd have to tweak the handlebars templates to get this sample closer to what we produce for our changelogs. We like giving authors credit and grouping all Rule-related changes under a rules section – instead of a section per rule. This is definitely a +1 from me to try integrating it into the build flow. @stevemao Do you have the command that you used to generate our changelogs handy? |
I can definitely tweak the templates for you. I will create a The sample log I generated was using |
What do we need to do now to use this? I'm ok with manually tweaking the changelog after running |
I have pushed several new releases and a ton of bugs have fixed. Would you still consider using it? |
@hzoo Hmmm... Not interested? |
Not at the moment, just closing things that we can come back to |
we have conventional-changelog or conventional-github-releaser (there are also grunt/gulp tasks) to automate the process of writing the changelog. As you are using formatted commit messages so the logs can be generated well according to the parts of the message. We use handlebars for templating the logs. It can also ignore reverted commits. There are many other features. We have a jquery preset for people using jquery commit format.
The modules are actively maintained.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: