Skip to content

ci: open an issue when the databases fail to build - #15

Merged
alviss7 merged 1 commit into
mainfrom
ci/notify-failures
Oct 20, 2026
Merged

alviss7 merged 1 commit into
mainfrom
ci/notify-failures

Conversation

@alviss7

@alviss7 alviss7 commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Problem

Databases runs are triggered by opengeoip-bot[bot] through repository_dispatch. GitHub sends the failure email to whoever triggered the run, so to the bot: the failures on October 16 and 17 went unnoticed.

Change

New Notify job, which runs after publish and image:

  • on failure, it opens a "Databases workflow failing" issue with the bug label and a mention of @alviss7. If that issue is already open, it adds a comment instead. The mention triggers the email notification.
  • after a successful run, it closes the open issue with a link to the run.

A cancelled run does nothing.

Runs are triggered by opengeoip-bot through repository_dispatch, so GitHub
sends its failure email to the bot and nobody hears about it. Open an
issue mentioning @alviss7, or comment on the open one, when a job fails,
and close it after the next successful run.
@alviss7
alviss7 force-pushed the ci/notify-failures branch from e94a72a to aed2ee0 Compare October 17, 2026 09:37
@alviss7
alviss7 merged commit 382aace into main Oct 20, 2026
2 checks passed
@alviss7
alviss7 deleted the ci/notify-failures branch October 20, 2026 04:39
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.

1 participant