Skip to content

Failure issue: a failed run nobody watched opens an issue, and closes it when it passes - #21

Merged
lana-20 merged 1 commit into
mainfrom
failure-issue
Oct 31, 2026
Merged

lana-20 merged 1 commit into
mainfrom
failure-issue

Conversation

@lana-20

@lana-20 lana-20 commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

A failed run nobody was watching now opens an issue. Today nothing does: a scheduled run, a push to main or a release tag can fail without a word to anyone.

.github/workflows/failure-issue.yml runs when Pages completes:

  • A failure or a timeout outside a pull request opens an issue titled " is failing", labeled ci-failure. It names the failed jobs and steps, the event, the branch or tag and the commit, and links the run, whose logs and artifacts are on its page. A later failure comments on the open issue rather than opening another.
  • The next run that passes comments and closes the issue, so the open ci-failure issues are what is broken now.
  • A pull request's runs are left out, since the pull request already shows them.

None of the existing workflows changes. workflow_run workflows run from the default branch, so this takes effect once merged. The same file goes into each mobiumdev repository with unattended workflows, listing that repository's own.

actionlint is clean, shell code included.

… it when it passes

A scheduled run, a push to main or a release tag that fails ([Pages]) opens
an issue labeled ci-failure, naming the failed jobs and steps and linking
the run; a later failure comments on it, and the next run that passes
closes it. A pull request's runs are left to the pull request.
@lana-20
lana-20 merged commit 1345191 into main Oct 31, 2026
2 checks passed
@lana-20
lana-20 deleted the failure-issue branch October 31, 2026 05:15
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