Ignore superseded dashboard publish cancellations#62
Conversation
There was a problem hiding this comment.
Pull request overview
This PR makes a targeted one-line change to the hourly Pull Request Dashboard workflow's failure-notification gate. Previously, the notify-hourly-failure job treated only a success result from the per-repository run-repo-dashboard matrix job as a non-failure. Because the called publish-dashboard job uses concurrency with cancel-in-progress: true, a run that is superseded by a newer publish surfaces as cancelled, which was incorrectly flagged as a failure and opened noisy workflow-failure tracking issues. The change now also treats cancelled as a non-failure. Genuine failures still report, since matrix result aggregation reports failure in preference to cancelled.
Changes:
- Treat a
cancelledresult fromrun-repo-dashboardas success for hourly backfill failure notifications, alongsidesuccess.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Treat cancelled per-repository dashboard runs as non-failures for hourly backfill notification purposes, so superseded publish jobs do not open noisy workflow failure issues while real failures still report.