-
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
Bring changelog up-to-date #3568
Conversation
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 76bf112 Collapsed results for better readability
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we only have the change-log for the most recent release, and then maybe have a link to the releases section of the github for everything else? Having the full change-log since day-zero can be a really long list, and this file would keep growing. We already have these changes in the release notes for each release.
Though most users and maintainers will likely use the GitHub releases page, it is still valuable to have all release notes inside of the codebase itself. For example, the project might at some point move to another platform. This is also commonly done in other projects, for example: |
Description
Use github.com/rhysd/changelog-from-release to automatically generate the changelog from the repository's releases.
Might be nice to have this as a GitHub Action.
master
branchFiles changed
in the Github PR explorer