Repository navigation
ci(release): never generate release notes - #80
Merged
Merged
Conversation
Moving a tag to republish a build ran the notes generator again, and each run added another "What's Changed" list under the release's own notes. They are now generated only when the release does not exist yet; a republished build keeps the notes it has.
A release's notes are written by hand, and the generated "What's Changed" list of pull request titles is not wanted on the page at all. This replaces the check for a new release with the generator switched off.
Soulhackzlol
changed the title
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
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.
What was wrong
Every time the
v0.1.16tag was moved to republish a build, the release workflow generated the notes again and appended them. The release ended up with three "What's Changed" lists under the written notes.Fix
The notes generator is switched off. A release's notes are written by hand, and the generated list of pull request titles is not wanted on the page.
A brand new release therefore starts with an empty description until its notes are written.
Also done, outside this PR
The 0.1.16 release text was cleaned by hand: no "What's Changed" list, and a section for chat games and points.
Checked
The workflow file parses. The publish step only runs on a tag push, so its first real run is the next release.