Skip to content

fix: correct Discord build attempt and recovery notifications - #175

Open
arnabnandy7 wants to merge 1 commit into
embabel:mainfrom
arnabnandy7:fix/discordBuildNotifications
Open

arnabnandy7 wants to merge 1 commit into
embabel:mainfrom
arnabnandy7:fix/discordBuildNotifications

Conversation

@arnabnandy7

Copy link
Copy Markdown

Fixes #174

Discord failure notifications linked to the overall workflow run, so a successful rerun left a stale failure message pointing to a successful build. Recovery detection also missed failed attempts within the same run.

This change replaces the shared notification workflows with a local implementation that:

  • Includes the commit SHA, attempt number, and exact attempt link.
  • Detects recovery after a failed attempt of the same run.
  • Preserves recovery detection across separate runs without repeating recovery messages after an already successful attempt.

Signed-off-by: Arnab Nandy <arnab_nandy7@yahoo.com>
@arnabnandy7
arnabnandy7 force-pushed the fix/discordBuildNotifications branch from d25b6a2 to 07f59d5 Compare October 25, 2026 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Discord build failure notification remains misleading after a successful rerun

1 participant