feat: notify Discord on release and add manual resend trigger#21
Merged
Conversation
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.
What
Adds Discord release notifications to the
release-pleaseworkflow, matchingmno-adapters-pm-model:discord-notify— on a real release (gated onrelease_created), calls the shared reusable workflow2060-io/organization/.github/workflows/discord-release-notify-call.yml@mainto post release notes to Discord.discord-notify-manual—workflow_dispatchwith anotify_taginput to (re)send a notification for an existing tag.release-pleasejob gated topushevents so manual runs only notify.Why this shape
The release is created with the default
GITHUB_TOKEN, sorelease: publisheddoes not trigger downstream workflows — we call the notifier directly. The webhook secret is passed explicitly (notsecrets: inherit) because the reusable workflow is in another org (2060-io) and inherited secrets aren't reliably forwarded across the org boundary.Follow-up
Add an Actions secret
DISCORD_UPDATES_WEBHOOK_URL(repo ormobieraorg). Without it the job runs but posts nothing (no failure).