Skip to content

[CI Health] CI Health Report — 2026-03-09 #178

@github-actions

Description

@github-actions

Repos scanned: 22 | Workflows inventoried: 238 | Overall health: ~75%

Generated by maintenance-ci workflow · 2026-03-09


Organization Summary

Status Workflows Repos
🟢 Healthy (≥90%) ~218 10
🟡 Warning (80–89%) 3 2
🔴 Critical (<80%) 3 3
⚪ Disabled 0 0
❔ Stale (>7d / no runs on default branch) 8 6

Failing Workflows

Repo Workflow Pass Rate Last Failure Trend
sdlc-quality CI ~90% (1 recent failure) 2026-03-01 📉 Declining
atlatl-spec Validate Specification ~70% (est.) 2026-03-07 📉 Declining
vscode-git-adr CI ~90% (1 recent failure) 2026-03-02 📉 Declining

Failure details:

  • sdlc-quality/CI — Failed on commit chore: update dependabot configuration. A routine Dependabot config change broke the CI workflow.
  • atlatl-spec/Validate Specification — Failed on commit fix: replace invalid <br/> with \n in Mermaid sequence diagram. The attempted fix (replacing HTML <br/> with \n in a Mermaid sequence diagram note) itself triggered a validation failure — the Mermaid linter still rejects the syntax. Persistent spec validation issue.
  • vscode-git-adr/CI — Failed on ci: bump actions/upload-artifact from 6 to 7 (#25) (Dependabot PR merged). The major version bump from v6→v7 of actions/upload-artifact introduced a breaking change in the workflow.

Disabled Workflows

No disabled workflows detected across managed repositories.


Stale Workflows (No runs in 7+ days)

Repo Workflow Last Run Notes
atlatl CI Checks (no runs on main) 0 runs on default branch — likely push-only trigger not yet activated
atlatl Code Coverage (no runs on main) 0 runs on default branch
lro-bench CI Checks (no runs on main) 0 runs on default branch — template repo, may not have active code
daedalus CI Checks (no runs on main) 0 runs on default branch — template repo pattern
homebrew-tap CI 2026-02-22 (15d ago) No recent pushes to default branch
homebrew-tap Test Formula 2026-02-22 (15d ago) No recent pushes to default branch
MIF Validate MIF Schemas 2026-02-22 (15d ago) No recent pushes to default branch
structured-madr Validate ADRs 2026-02-16 (21d ago) Only 3 total runs; low activity repo

Per-Repo Health Scores
Repo Health Score Workflows Failing Stale / No CI
.github 95% 35 0 0
github-project-manager 95% 3 0 0
rlm-rs 90% 18 0 0
rlm-rs-plugin 90% 4 0 0
git-adr 95% 8 0 0
adrscope 90% 12 0 0
adr 90% 4 0 0
human-voice 90% 3 0 0
documentation-review 90% 3 0 0
subcog 85% 14 0 0 (PR pending approval)
sdlc-quality 40% 5 1 (CI) 0
atlatl-spec 40% 5 1 (Validate Specification) 0
vscode-git-adr 40% 7 1 (CI) 0
homebrew-tap 45% 7 0 2 (>15d stale)
MIF 45% 5 0 1 (>15d stale)
structured-madr 40% 5 0 1 (>21d stale)
atlatl 30% 31 0 2+ (no runs on main)
lro-bench 30% 30 0 2+ (no runs on main)
daedalus 30% 30 0 2+ (no runs on main)
ccpkg N/A 6 0 No dedicated CI workflow
refactor N/A 1 0 No CI (Dependabot only)
memory-capture-plugin N/A 2 0 No CI (Dependabot only)
Common Failure Patterns
  • Dependabot major version bump breaking CI — seen in 2 workflows across 2 repos:

    • vscode-git-adr/CI: actions/upload-artifact v6→v7 introduced a breaking API change
    • sdlc-quality/CI: Dependabot config update triggered a CI failure (indirect)
    • Recommendation: Add a CI gate that runs on Dependabot PRs before auto-merging major version bumps
  • Mermaid/spec validation failures — seen in 1 workflow, 1 repo:

    • atlatl-spec/Validate Specification: Mermaid sequence diagram notes do not support HTML tags (<br/>), and the attempted fix (using \n) also failed validation. The spec linter appears to have strict requirements not well-understood by contributors.
    • Recommendation: Add a local pre-commit hook or editor extension for Mermaid validation to catch this before push
  • Template repos with zero CI runs on main — pattern across 3 repos:

    • atlatl, lro-bench, daedalus all use the same template with 30+ workflows but CI Checks / Code Coverage have never run on main
    • These workflows are likely triggered by push events that don't occur on main (only feature branches), or the repos are early-stage with no code changes merged yet
    • Recommendation: Verify trigger conditions for these template workflows; consider adding workflow_dispatch triggers for manual validation
  • Inactive repos with stale CI — pattern across 4 repos:

    • homebrew-tap, MIF, structured-madr have not had CI runs in 15–21 days
    • These repos appear to be low-activity; no action required unless expected to be active

Generated by maintenance-ci · Run ID: 22848465853

Generated by Maintenance CI

Metadata

Metadata

Assignees

No one assigned

    Labels

    gpm/reportGPM automated report

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions