Automate generation of release notes further#1563
Merged
Merged
Conversation
squell
force-pushed
the
automate-release
branch
3 times, most recently
from
bb5e0b3 to
c1b31f7
Compare
Member
Author
|
I have tested this CI work flow and it works like a charm! |
squell
force-pushed
the
automate-release
branch
from
c1b31f7 to
fc2e6a7
Compare
bjorn3
reviewed
May 26, 2026
bjorn3
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Last few releases I was simply following an algorithm, so let's code that.
This automates the generation of the header (about the binaries) and the contributor list.
Note: it could be sped up by caching the list of contributors in the repo. But right now fetching all the PR's is still doable and that should remain the case for quite some time.