questrail / arghelper / 33538601836
100%

DEFAULT BRANCH: master
Ran
Jobs 1
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: 100.0%. Remained the same
33538601836

push

github

matthewrankin 
Stop explaining the workflows by a job that never existed

Two comments reasoned about a dependency floor job. ci.yml justified
UV_NO_SYNC by saying a re-sync there "would quietly undo the lowest-direct
install the job exists to test", and release.yml said publishing "waits on
the whole matrix and on the dependency floor job".

There is no such job, and there never has been. git log -S floor puts both
comments in the commit that added the workflows, with no job to match; they
came from applyaf and siganalysis, which have runtime dependencies worth
resolving at their floor. arghelper has none, so a floor job here would
pin nothing but the dev tools that uv.lock already pins.

The comments in this repository carry the reasoning, which is why the wrong
one costs something. A reader who goes looking for the floor job to
understand UV_NO_SYNC finds nothing and has to work out whether the job or
the comment is the mistake. UV_NO_SYNC has a reason that stands on its own
in a repository with two jobs: without it every uv run re-resolves on top
of the uv sync --locked that just ran, and that second resolution is one
nothing checks against the lock file. release.yml now names what the ci job
actually gates the publish on, which is the version matrix and the workflow
audit.

Claude-Session: https://claude.ai/code/session_017f1DUjNbmbbRW4djpsaq1y

31 of 31 relevant lines covered (100.0%)

1.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33538601836.1 1
100.0
 GitHub Action Run
Source Files on build 33538601836