Create a release announcement discussion automatically - #421
Merged
Conversation
The release tarball workflow now links each published release to the Announcements discussion category, which makes GitHub create the announcement post from the release notes. This restores the pattern used up to v5.1.0 and keeps org Discussions in sync with releases without a manual step.
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
1 participant
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.
Release announcements in org Discussions stopped after v5.1.0, because they relied on manually ticking Create a discussion for this release when publishing.
This adds a step to the existing
release.yml(which already runs on every published release): if the release has no linked discussion yet, it PATCHes the release withdiscussion_category_name=Announcements, which makes GitHub create the announcement post from the release notes. Idempotent, and a no-op when the checkbox was ticked manually.v7.0.0 and v7.1.0 were backfilled the same way (#419, #420), which confirms the PATCH approach works with these categories.