-
Notifications
You must be signed in to change notification settings - Fork 162
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
Please add a changelog #113
Comments
Yeah, we should have a CHANGELOG file, in my opinion. But how to maintain it? Do you now some automated way to generate a summary of the changes? If so, I could run on Travis or locally before tagging each release. |
zest.releaser https://github.com/zestsoftware/zest.releaser will update a history/changes file |
For small projects I just look at the list of commits between tags and copy the info from the PR merge commits into the readme. |
Take a look on https://keepachangelog.com, it's better to do it manually instead of automatically |
🤷🏽 it’s better to have something than nothing, waiting for perfection |
Hello! There is no information about the changes contained in a release.
A short list included in the README and/or PyPI description and/or github «release» tab would be great.
Thanks!
The text was updated successfully, but these errors were encountered: