Update Changelog Format #400
Labels
area:documentation
Relating to the documentation
difficulty:easy
A simple task appropriate for newcomers to the codebase
type:chore
Part of regular code upkeep
Description
I would like to see the
CHANGELOG.md
being generated from conventional commits. This specifically allows end-users to see, at a glance, what breaking changes there are (and how to migrate), what new features have been introduced, what bugs have been fixed, etc.As a concrete example, the changelog for versions
2.0.0
through to2.1.0
would look like this using commitizen's changelog function:While this is a good start, there are a couple of things I would like to change from commitizen's output:
### Contributors
in each section and (ideally) highlight new contributors.Motivation
The existing changelog is extremely verbose, reporting every commit's headline. This is, in my opinion, not very useful for end-users and I would like to see.
For example, looking at the existing changelog for version
2.0.0
to2.1.0
there are a lot of chore items which have no impact to the downstream users. Furthermore (and more concerning), the changelog makes no mention of dropping support for Python 3.6 and 3.7.Have you tried building it?
Not yet; seeking community feedback first
Self-service
The text was updated successfully, but these errors were encountered: