bleedingdeacons / hand / 34380338160
93%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 18
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: 92.943%. Remained the same
34380338160

push

github

web-flow 
ci: add the Windows head as a job that is off by default (#58)

The Windows head stopped compiling on 2026-09-01 and nobody found out
for eight releases, because this workflow builds Android and iOS and
nothing else. #57 fixed the head; this is the reason it went unnoticed.

The job is added disabled. It runs on neither a push nor a pull request,
so it gates no merge and costs no runner minutes, and it is deliberately
absent from the version job's `needs:` -- a skipped job makes its
dependents skip too, so listing it there while it is off would stop
every release.

Two ways to run it. workflow_dispatch runs it once by hand, and from a
branch rather than main: the version job is gated on refs/heads/main, so
a dispatch there would cut a release alongside the check. Setting the
repository variable HAND_BUILD_WINDOWS to `true` turns it on everywhere
without editing this file, which is also the moment to add `windows` to
that `needs:` list.

WHY OFF RATHER THAN ON. Turning it on immediately makes a fourth thing
that can go red on every pull request, and this head has no CI history
at all -- nobody knows yet whether windows-latest builds it reliably, on
what timing, or how often the image moves under it. The iOS job's own
comment records learning that sort of thing the hard way. Prove it by
dispatch first.

WHY A JOB AT ALL, IF IT DOES NOT RUN. Because the alternative is what
this file already tried. The Windows and MacCatalyst jobs were deleted
once, and the header paragraph claiming they were still available by
hand outlived them by weeks. A disabled job is visible in every run's
job list as a skip; a deleted one is visible nowhere, and has to be
written from scratch by whoever next needs it -- which is why the last
one never was. The header is updated to say what is actually true now,
since that is the exact failure it warns about.

A compile gate, not an artifact. No Release build and nothing uploaded:
a shippable Windows build means MSIX packaging and ... (continued)

1396 of 1502 relevant lines covered (92.94%)

1261.52 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34380338160.1 18
92.94
GitHub Action Run
Source Files on build 34380338160