Add a CHANGELOG
See original GitHub issueIs there one? Can someone add one?
I saw a new 0.5.1
release and couldn’t find the changes easily.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Keep a Changelog
A changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project. Why keep...
Read more >Changelog entries - GitLab Docs
Writing good changelog entries ... A good changelog entry should be descriptive and concise. It should explain the change to a reader who...
Read more >How To Automatically Generate A Helpful Changelog From ...
Creating a changelog is a usual task if a new software version is going to be released. It contains all the changes which...
Read more >What is Changelog & Example of ARN Change Log Format
What is a good changelog? · Always include a complete history of notable changes. · Include the “when” for each of the updates....
Read more >Sample CHANGELOG - gists · GitHub
Sample CHANGELOG. GitHub Gist: instantly share code, ... PROJECTNAME-TTTT PATCH Add logic to runsheet teaser delete to delete corresponding schedule cards.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello! Thank you for poking about the topic - we’ve wanted to do that for some time and the day to do that has finally come. I’m going to add release notes via djoser Github releases (available at https://github.com/sunscrapers/djoser/releases).
Please note that it’s ongoing process and there is some manual work to do. Also - unfortunately, idea about extracting release notes from commit messages is not good enough, because some commits didn’t precisely specify what they are about.
When I’m done with properly describing releases I’ll aggregate these notes into CHANGELOG file as proposed in issue.
I don’t know of any, but a quick google search showed this on first spot. Maybe worth a look: https://pypi.python.org/pypi/gitchangelog