coverallsapp / github-action / 31849881674
67%
master: 67%

LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran
Jobs 4
Files 1
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.667%. Remained the same
31849881674

push

github

web-flow 
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) <noreply@anthropic.com>

* 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 `smo... (continued)

2 of 3 relevant lines covered (66.67%)

2.67 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31849881674.1 1
66.67
 GitHub Action Run
2 31849881674.2 1
66.67
 GitHub Action Run
3 31849881674.3 1
66.67
 GitHub Action Run
4 31849881674.4 1
66.67
 GitHub Action Run
Source Files on build 31849881674