Coverage decreased (-0.01%) to 92.107% when pulling 917d66b on Visya:patch-1 into d3c2432 on conventional-changelog:master.

Coverage decreased (-0.01%) to 92.107% when pulling 917d66b on Visya:patch-1 into d3c2432 on conventional-changelog:master.

@Visya looking through Angular's changelog I don't see CI, Docs, or other commit types published. Does this change break how Angular currently generates their changelog?

cc @damianopetrungaro I believe this need is completely legitimate, but maybe not for the Angular configuration. What are your thoughts on how we can meet this need?

Hi @hutson

You're right, Angular doesn't include anything except feat, fix and revert in their changelog unless it's a breaking change (angular/angular#5672).

My reasoning was that it's nice to see all changes associated with the release, but on the other hand it can be seen as redundant for the user to see changes in the changelog that do not impact functionality. Maybe, a way to go would be to add this as a configuration option?

wanted to chime in that i would love a "config" option that allows us to override the defaults. While i don't have the bandwidth to manage a PR right now if this seems a viable route i'll look into it

I don't think we should change angular config. We can create a new config.

@Visya Thanks for this. We've been using this fix in saltstack-formulas/template-formula/release.config.js and it is working perfectly.

I feel the answer right now is to leave the angular preset unmodified, and encourage anyone wanting a slightly different output to create a fork of the angular preset with their changes.

Long-term, @bcoe is looking at supporting preset configuration in #421. A change that will hopefully meet your needs @Visya

@hutson I agree, I'm hoping that the conventional-changelog-conventionalcommits preset will create a good foundation for an easier to config preset that adheres explicitly to conventionalcommits.org.

Closing in favour of #421