ci: open a discussion with each release - #97
Merged
Conversation
A release is a one-way post: notes go out, and there is nowhere for anyone to say anything back. Discussions were enabled on the repository but the release that just shipped had no thread attached, so replying meant opening an issue. Each release now opens an Announcements thread. Announcements rather than General because only maintainers can start threads there, which suits a release, while anyone can still reply. Deliberately a separate step from the release itself, and non-fatal. Passing --discussion-category to `gh release create` would tie the two together, and a renamed or missing category would then fail a release whose notes were already correct. Publishing is the job; the thread is the nicety. A failure here logs a warning naming the likely cause and leaves the release standing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ToCUNy2SqwvfTq4a6xfSk1
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.
A release is a one-way post: notes go out, and there is nowhere for anyone to say anything back. Discussions were enabled on the repository but the release that just shipped had no thread attached, so replying meant opening an issue.
Each release now opens an Announcements thread. Announcements rather than General because only maintainers can start threads there, which suits a release, while anyone can still reply.
Deliberately a separate step from the release itself, and non-fatal. Passing --discussion-category to
gh release createwould tie the two together, and a renamed or missing category would then fail a release whose notes were already correct. Publishing is the job; the thread is the nicety. A failure here logs a warning naming the likely cause and leaves the release standing.Claude-Session: https://claude.ai/code/session_01ToCUNy2SqwvfTq4a6xfSk1