feat(changelog): handle BREAKING CHANGE from footer

[gotson]

Fixes #809

Context

Introduces a new ConventionalCommit subtype of Commit, which parses the commit body according to conventional commit specification. The conventional-commit preset uses a custom changelog.format instead of replacers to achieve formatting. The changelog presets can now have a custom format.

Checklist

• Review Contribution Guidelines.
• Make sure all contributed code can be distributed under the terms of the
  Apache License 2.0, e.g. the code was written by
  you or the original code is licensed under a license compatible to Apache License 2.0.
• Update documentation when applicable.

[CLAassistant]

All committers have signed the CLA.

[gotson]

The documentation may need some updates, but i am not sure what !

[aalmiray]

It’s OK, I can take care of the docs. Thank you for the PR! 😁

[gotson]

I haven't included yet any change about #806, i wanted to tackle things one at a time. If that PR gets merged, i will have a look at that afterwards.

[aalmiray]

PR failed because of missing license headers. Please invoke ./gradlew licenseFormat && ./gradlew check before pushing one more time.

[gotson]

PR failed because of missing license headers. Please invoke ./gradlew licenseFormat && ./gradlew check before pushing one more time.

Would that make sense to add the need to run ./gradlew licenseFormat to the Contribution Guidelines ?

[gotson]

On top of the above requested changes, i have also:

• prefixed the name of the properties for the Mustache context with conventionalCommit to avoid confusion
• introduced a separate ccBody field instead of using the existing Commit.body, which i noticed was used by the labelers with regex.

[gotson]

I'm putting this back to draft, for some reason i can't get the mustache context to contain the additional properties anymore. It used to work, and doesn't since my latest changes, but i have no idea why.

[gotson]

I found the problem, should be ready for review!

[aalmiray]

Looking pretty good! I wonder if the concept of trailers should be added to the base Commit class a well. We can of course revisit this idea after this PR has been merged.

[aalmiray]

Thanks! 😄

[gotson]

Looking pretty good! I wonder if the concept of trailers should be added to the base Commit class a well. We can of course revisit this idea after this PR has been merged.

Yes, good idea, since conventional commits follows the standard git trailers convention. Could be used for the contributors i think!