Repository navigation
ci(savings): a failed nightly run opens an issue, or comments on the open one - #293
Merged
Merged
Conversation
…open one The savings watermark job does not run on pull requests, so its failures reach nobody: from 2026-10-02 to 2026-10-22 it failed every night without anyone seeing it. The maintainer chose an issue as the alarm (2026-10-24), over running the job on every pull request that touches src/, which would add 16 to 21 minutes of CI to each. - A new last step runs when a scheduled run fails. It comments on the open issue titled "Savings watermark failed on main", or opens one, with the run's link. GitHub then mails the maintainer. One issue covers a streak of red nights; closing it after the fix re-arms the alarm. - `permissions` is now `contents: read` and `issues: write`. The token needs nothing else: the checkout reads, and the cache does not use it. - The manual dispatch gains `simular_falha`, which fails the first step before any build. The expensive steps are then skipped, and the alarm runs as on a red night. This is how the alarm was proved. Proved on this branch, with two dispatches at simular_falha=true: - run 40148177331: the first step failed, the seven build steps were skipped, and the alarm opened issue #292; - run 40148205543: the alarm commented on #292 and opened no second issue (one open issue with that title, one comment). #292 was closed afterwards, with a comment saying both failures were simulated. The YAML parses, with the steps in this order. actionlint is not installed here, so the workflow was proved by those two runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LyLm7Q1o7kCHngE63BnoTx
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The savings watermark job runs only at night and on demand, never on a pull request. So its failures reach nobody: from 2026-10-02 to 2026-10-22 it failed every night without anyone seeing it. The maintainer chose an issue as the alarm (2026-10-24), over running the job on every pull request that touches
src/(+16 to 21 minutes of CI each).permissionsis nowcontents: readandissues: write.simular_falha. It fails the first step before any build, so the expensive steps are skipped and the alarm runs as on a red night. This is how the alarm was proved.Proof
Two dispatches of this branch's workflow, with
simular_falha=true:#292 was closed afterwards, with a comment saying both failures were simulated. The YAML parses, with the steps in that order.
actionlintis not installed here, so the workflow was proved by those two runs.🤖 Generated with Claude Code
https://claude.ai/code/session_01LyLm7Q1o7kCHngE63BnoTx