-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
Comments
Yeah, saw that as soon as I published it... PR incoming shortly :) EDIT: Fix is at #401 |
Merged
Yep, this makes sense to me, we use conventional commits for changelogs across multiple pact foundation repos I believe, and agreed there is lots of noise in the release notes that may not be of relevance to users. (whats news, and whats breaking are what I really care about) |
Implemented by #567 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: