Repository navigation
Commit 0a06e5d
Smoke test: run weekly and open an issue on failure (#270)
* Smoke test: add weekly schedule
The existing `workflow_run` trigger only fires after releases of *this* repo,
so it never catches changes underneath us -- a new coverage-reporter release,
a runner-image update, or a Homebrew change. Those are precisely the drifts
that break the end-user install chain silently.
Concrete example: coverage-reporter v0.6.18 shipped tonight and nothing here
fired. Verifying it required remembering this workflow existed and dispatching
it by hand, which is exactly the kind of step that gets skipped.
Adds a weekly cron as a safety net. The job's existing `if:` guard already
passes for schedule events (`github.event_name` is 'schedule', so the
workflow_run conclusion check is short-circuited), so no other change needed.
Chose a weekly schedule over wiring a `repository_dispatch` from
coverage-reporter's build.yml: cross-repo dispatch cannot use
`secrets.GITHUB_TOKEN` and would require creating, storing, and rotating a PAT.
A schedule needs no credentials and additionally covers drift that no
coverage-reporter release would trigger -- which is where two of tonight's
three breakages actually came from.
Cron is set off the hour to avoid GitHub's peak-of-hour scheduling delays.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
* Smoke test: open an issue on failure
Email is a weak alarm for a scheduled job. GitHub sends scheduled-run failure
notifications only to whoever last edited the cron expression -- not to repo
watchers -- and if that person's notification settings are wrong, the failure
is silent. We would have automated the check without automating the alert,
which is worse than not automating it: it looks watched when it is not.
Adds a `report-failure` job that opens an issue when any smoke matrix job
fails. Visible, persistent, and independent of anyone's inbox configuration.
Details:
- Reuses the existing open issue (via the `smoke-test-failure` label) and
comments on it, so a recurring weekly failure does not open 52 issues.
- Creates the label on first use, so no manual setup is required.
- Scoped `permissions: issues: write` on the job rather than the workflow.
- The issue body explains what the failure implies (end users are likely
broken right now, even though nothing in this repo changed) and lists the
usual causes, so whoever picks it up has context rather than a bare link.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
---------
Co-authored-by: Claude Opus 5 (1M context) <[email protected]>1 parent 87358ce commit 0a06e5d
1 file changed
Lines changed: 67 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
7 | | - | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
8 | 9 | | |
9 | 10 | | |
10 | 11 | | |
| |||
18 | 19 | | |
19 | 20 | | |
20 | 21 | | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
21 | 28 | | |
22 | 29 | | |
23 | 30 | | |
| |||
56 | 63 | | |
57 | 64 | | |
58 | 65 | | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
| 119 | + | |
| 120 | + | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
0 commit comments