[RFC] Move to conventional commit and conventional changelog

[JellyBellyDev]

Hi @garak @AlessandroMinoccheri @antonkomarev

WDYT about to move in a conventional commit and conventional changelog way?

If we do this we could automate the process of generating a new release and updating the changelog file automatically.

I tried this flow in my personal repo with an github action: https://github.com/JellyBellyDev/ImageOrientationFix/blob/master/.github/workflows/release.yml

How it works: when we would generate a new release go to tab actions, select "Create release" workflow, and click on "Run workflow".
The workflow will do:

• choose new bump version (from conventional commits)
• update the file changelog
• commit file changelog updated
• push new tag and release tag

Ref:

• https://www.conventionalcommits.org/en/v1.0.0/
• https://github.com/conventional-changelog/conventional-changelog-config-spec/blob/master/versions/2.1.0/README.md

Example:
See the last two release:
https://github.com/JellyBellyDev/ImageOrientationFix/releases
https://github.com/JellyBellyDev/ImageOrientationFix/blob/master/CHANGELOG.md

WDYT?

[garak]

It looks good to me, but then we should validate the commit messages. In your personal repo it's easy since you're the only committer, but it's not the same here.

[JellyBellyDev]

Exactly!
If you liked the idea, my second question would have been about validating commit messages.
Which tool would you prefer?
Would you prefer to add a tool on the githook side or a control on the CI side?

[garak]

A GitHub action would be better for me

[JellyBellyDev]

WDYT?
#105