IF Commons GitHub

Workflows

The last runs of each workflow on main. A mark is a run, newest first: ✓ passed, ✗ failed, – cancelled or skipped, … running. A workflow that flips between passing and failing is marked as flapping.

WorkflowLatestWhenMinutesLast runsFlapping
ciqueued2026-11-22 16:40 UTC0… … ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
conformancesuccess2026-11-22 16:38 UTC2✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✗ ✓
evidencesuccess2026-11-22 16:14 UTC12✓ ✗ ✓ ✗ ✗ ✓ ✓ – ✓flapping (4 flips in 8 runs)
releasesuccess2026-11-22 15:04 UTC4✓ ✓ ✓ ✓ ✓ ✗ ✗ ✗ ✓ ✓
sitepending2026-11-22 16:40 UTC0… … – – ✓ – – ✓ ✓ –
testsin_progress2026-11-22 16:40 UTC1… ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

Reliability and speed

From the runs above, cancelled ones left out: the share that passed, the median minutes a run takes, and how long a failure usually lasts (from a run that failed to the next that passed).

WorkflowRunsPassedMedian minutesMedian time to recover
ci2868%1014 min
conformance1593%169 min
evidence863%14274 min
release2232%41408 min
site10100%8
tests2568%292 min

Delivery

The four measures of DORA, taken from the runs of the workflow that publishes the site (10 runs over 0.1 days). They describe how this repository delivers its documentation, which is a proxy for delivery: a release has its own runs.

MeasureValueMeaning
Deployment frequency163.8 a dayPublishes that succeeded, per day of the window.
Lead time8 minMedian minutes a successful run took, from its start to its publish.
Change failure rate0%Runs that failed, of those that finished (cancelled runs left out).
Time to restoreMedian minutes from a failed run to the next one that passed.

ci: jobs that failed

RunJobStep
#369 build policy: the workflow files check runs on Bun and on NociThe findings, merged; the pipeline is sound where every cell that ran left its file (ci/collect.ts)
#368 build policy: the workflow files check is the red cause workciThe findings, merged; the pipeline is sound where every cell that ran left its file (ci/collect.ts)
#367 repoctl ci step, the linter's report in a pipeline's log, anciThe findings, merged; the pipeline is sound where every cell that ran left its file (ci/collect.ts)

conformance: jobs that failed

RunJobStep
#17 Merge remote-tracking branch 'origin/main' into claude/pensiotel-conformanceThe development tools, from bun.lock

evidence: jobs that failed

RunJobStep
#8 evidencefindingsThe findings, merged; the pipeline is sound where every cell that ran left its file (ci/collect.ts)
#6 evidencecollectWhich run this is
#5 evidencecollectWhich run this is

release: jobs that failed

RunJobStep
#17 releasebuild (commons 0.2.0)verify, which includes the packing
#16 releasebuild (anyfs 0.1.0)verify, which includes the packing
#15 releasebuild (docs 0.3.6)verify, which includes the packing

tests: jobs that failed

RunJobStep
#345 0038-build-policy: the registry row says in force, as the otcheckThe formatter
#344 0038-build-policy: findings, never failures; the red causes,windowsCommons' generated files and specifications, on Bun and on Node 26
#344 0038-build-policy: findings, never failures; the red causes,checkThe formatter
#344 0038-build-policy: findings, never failures; the red causes,tests (ubuntu-latest, node)The tests on Node 26
#344 0038-build-policy: findings, never failures; the red causes,tests (ubuntu-latest, bun)The tests on Bun (tests/release/ is the release's: it packs, installs and type-checks every library)
#344 0038-build-policy: findings, never failures; the red causes,tests (macos-latest, node)The tests on Node 26
#344 0038-build-policy: findings, never failures; the red causes,tests (macos-latest, bun)The tests on Bun (tests/release/ is the release's: it packs, installs and type-checks every library)
#343 planning-query: declare npm like every library, with its paccheckThe formatter

Titles, headings, exports, tables, columns and requirements. Esc closes.