-
Notifications
You must be signed in to change notification settings - Fork 255
Remove commit types from subjects in CHANGELOG #924
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
Comments
@paduszyk Thanks for the report, I am working this effort it's just taken me some time to make it public in lieu of other priorities. There is a milestone for improved changelogs that I'm consolidating all of them. Feel free to check out what is planned and add what you would like to see as well. |
@paduszyk, one thing I forgot to mention is that if you wanted to see this resolved in your own projects today, you can easily define your own custom changelog template and apply it to your projects. |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
Still on the backlog, these changes were put on hold while I attended to other improvements and fixes |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
Likely not going to be changed until |
🎉 This issue has been resolved in version 9.13.0 🎉The release is available on: |
Description
Hey ✋🏻 First of all, thanks for such a great project! 💚
Changelog summarizes changes grouped by types - in the case of the Angular scheme, the type is simply the semantic prefix of the message:
ci
,chore
,feat
, etc. Within the given type, all the commits are listed with the prefix repeated, like that:so, the prefix is repeated for each commit. I think that removing commit types (and capitalizing the subject) would result in a cleaner CHANGELOG:
Use cases
Removing prefixes will reduce redundancy.
Possible implementation
This issue is to share my idea. I don't know how to implement it, I haven't dug into the codebase yet...
The text was updated successfully, but these errors were encountered: