mirror of
https://github.com/LearningCircuit/local-deep-research.git
synced 2026-06-14 02:55:03 +03:00
The auto-regenerated workflow-status.md on every version-bump PR produced ~15 rows of churn that wasn't signal: - Status emoji column flipped between ✅ / · / ⏳ depending on which event last ran (e.g. backwards-compatibility flipped ✅→· because the most recent run was a skipped workflow_call, not because it regressed). The live badge column to its right is the source of truth for current status anyway, and run history lives in GitHub Actions itself. Drop the column. - Last activity buckets oscillated across this week / last week / 2 weeks ago for healthy daily/weekly workflows. Coarsen to last 30 days / 1-3 months ago / 3-6 months ago / long ago / never so a healthy workflow sits in one bucket indefinitely. Net effect: regenerations in steady state produce zero diff. Real signal (new stale/disabled workflows, aging past the 30d bucket) still surfaces.
20 KiB
20 KiB
Workflow Status
Live status of every GitHub Actions workflow in this repo. Auto-generated by
scripts/generate_workflow_status.py. Do not edit between the generated markers — regenerate withpdm run python scripts/generate_workflow_status.py. Anything outside the markers is preserved on regeneration.
How to read this page
- Live badges (right column on active gates) re-render on every page
view and reflect the current head-of-default-branch status from
GitHub. Click one to land on that workflow's runs page. The badge is
the source of truth for current status — there is intentionally no
static status column, because that would flip every regeneration as
the most-recent run cycles through
success → skipped → in_progress. - Last activity uses coarse calendar buckets —
last 30 days,1-3 months ago,3-6 months ago,long ago,never. Exact dates would change every regeneration; buckets only change when a workflow drifts, which is the signal worth seeing in version-bump diffs. - Disabled = a caller has the
uses:line commented out, or the workflow is disabled in the GitHub UI. Stale = scheduled trigger but no successful run within 2× its cron cadence (and ≥60 days). The three top sections are the action items. - Reusable workflows (those triggered only by
workflow_call:) show their gated run — the most recent run of their parent (release.yml, release-gate.yml, ci-gate.yml) that included them — not their own empty direct-run history.
65 workflows: 1 disabled · 1 stale · 2 manual-only · 61 active
⚠ Disabled workflows
| Workflow | Disabled where | Last direct run |
|---|---|---|
nuclei.yml |
release-gate.yml:177 (commented) |
never |
⚠ Stale (scheduled but no recent successful run)
| Workflow | Cron | Last successful run |
|---|---|---|
update-precommit-hooks.yml |
0 8 * * 5 |
never |
ℹ Manual-only by design
| Workflow | Last manual run | Trigger |
|---|---|---|
check-config-docs.yml |
1-3 months ago | manual |
sync-main-to-dev.yml |
1-3 months ago | manual |
Release-blocking gates — daily (release-gate cron 02:00 UTC)
Release gates — release-time only
Scheduled (own cron)
PR / push checks
Repository-dispatch publishers
| Workflow | Last activity | Trigger | Live badge |
|---|---|---|---|
docker-publish.yml |
last 30 days | repo_dispatch | |
prerelease-docker.yml |
last 30 days | repo_dispatch | |
publish.yml |
last 30 days | repo_dispatch |
Other
| Workflow | Last activity | Trigger | Live badge |
|---|---|---|---|
issue-research.yml |
last 30 days | issues | |
ldr-research-reusable.yml |
never | workflow_call |