Use conventional commits and commit linter?

[janfb]

For previous releases we crafted the CHANGELOG.md by hand. For the upcoming release this is a lot of work. So I looked into automated tools and came across:

• https://www.conventionalcommits.org/en/v1.0.0/ and
• https://github.com/conventional-changelog/commitlint?tab=readme-ov-file

A commit message convention and a linter that checks commit messages 🚓

I really like the idea, most importantly because it supports automatic generation of CHANGELOGs and semantic versioning.

any thoughts?

[michaeldeistler]

Depends on how well it works I guess :) If it just copies PR descriptions (or commit titles) then I think the resulting CHANGELOG will not really helpful, but if it has some LLM to filter relevant content then it might be great.

[janfb]

let's just try to follow this convention when we do squash commits for PRs onto main. This will make it easier to order the commits on main.

For the changelog it will just be a lot of work for the upcoming release, but otherwise I noticed that GitHub already offers creating a list of all commits since the last release when one creates the entry on GitHub.