Skip to content

fix(ci): make fork nightly Discord failure notification reliable - #165

Merged
incognitojam merged 1 commit into
mainfrom
t3code/update-discord-failure-notification
Aug 16, 2026
Merged

fix(ci): make fork nightly Discord failure notification reliable#165
incognitojam merged 1 commit into
mainfrom
t3code/update-discord-failure-notification

Conversation

@incognitojam

Copy link
Copy Markdown
Collaborator

What Changed

Replaced the Discord webhook action in the fork nightly workflow with a direct curl request that builds the payload using jq, retries transient failures, and fails when Discord rejects the notification.

Why

The nightly failure notification was not reliable enough. The new implementation makes the request and payload construction explicit, preserves the failure details and workflow link, and adds retry handling for transient errors.

Checklist

  • This PR is small and focused
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes

- Build the Discord payload explicitly with jq
- Retry webhook delivery and fail visibly on notification errors
@incognitojam
incognitojam force-pushed the t3code/update-discord-failure-notification branch from c3aeb22 to 172503f Compare August 16, 2026 09:20
@incognitojam
incognitojam enabled auto-merge (squash) August 16, 2026 09:20
@incognitojam
incognitojam merged commit 9e03162 into main Aug 16, 2026
8 of 9 checks passed
@incognitojam
incognitojam deleted the t3code/update-discord-failure-notification branch August 16, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant