githubnext / githubnext/gh-aw-cao
[self-care:open-source-failures] Open-source workflow failure digest for 2026-09-05 snapshot
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
Snapshot 2026-09-05T07:59:11.515Z covers the last 168 hours across 7 public projects and captured 1268 failed runs in the bounded activity snapshot. I found 7 evidence-backed clusters: 2 P0, 4 P1, and 1 P2. No open tracking issues with the configured prefix were found, so the highest-value gaps are the live-mode target-authority failures blocking `githubnext/gh-aw-cao` workflows and the repeated GitHub App token failure in AI Credit Savings.
**Action:** CAO maintainers should restore target authority for the blocked live workflows first; accept when new runs of the affected workflows pass pre_activation without the target-authority error.
Prioritized remediation list:
1. `githubnext/gh-aw-cao` — target authority missing in pre_activation across AW Doctor workflows (P0, 15 runs).
2. `githubnext/gh-aw-cao` — target authority missing in pre_activation for Dependabot Release Trains (P0, 4 runs).
3. `githubnext/gh-aw-cao` — GitHub App token generation fails in AI Credit Savings (P1, 5 runs).
Critical findings:
- The strongest blocking pattern is `Target authority missing: add .github/workflows/cao.json to the target default branch for live mode`.
- Bounded evidence also shows a likely shared safe-output processing problem in `SelfCare` and `Dev Practices / Well-Architected` (P1, 6 runs).
- `githubnext/gh-aw-workshop` has a separate shared activation-artifact upload failure pattern (P1, 5 runs).
- The snapshot includes some conclusion-only failures; those were kept separate unless they corroborated a stronger enriched signature.
Cluster summary
- P0 — `githubnext/gh-aw-cao`; workflows: `.github/workflows/aw-failures-investigator.lock.yml`, `.github/workflows/aw-maintenance-compiler-security.lock.yml`, `.github/workflows/aw-maintenance-upgrade.lock.yml`; signature: `Target authority missing: add .github/workflows/cao.json to the target default branch for live mode`; runs: 15; representative: https://github.com/githubnext/gh-aw-cao/actions/runs/33953571548; confidence: high.
- P0 — `githubnext/gh-aw-cao`; workflow: `.github/workflows/dependabot-release-train-updater.lock.yml`; signature: `Target authority missing: add .github/workflows/cao.json to the target default branch for live mode`; runs: 4; representative: https://github.com/githubnext/gh-aw-cao/actions/runs/33952507584; confidence: high.
- P1 — `githubnext/gh-aw-cao`; workflow: `.github/workflows/optimization-ai-credit-optimizer.lock.yml`; signature: `Generate GitHub App token`; runs: 5; representative: https://github.com/githubnext/gh-aw-cao/actions/runs/33952586870; confidence: medium.
- P1 — `githubnext/gh-aw-cao`; workflows: `.github/workflows/self-care.lock.yml`, `.github/workflows/software-development-practices-github-well-architected.lock.yml`; signature: `Process Safe Outputs`; runs: 6; representative: https://github.com/githubnext/gh-aw-cao/actions/runs/33953401010; confidence: medium.
- P1 — `githubnext/gh-aw-workshop`; workflows: `.github/workflows/title-similarity-review.lock.yml`, `.github/workflows/workflow-skills-editor.lock.yml`, `.github/workflows/workshop-author.lock.yml`, `.github/workflows/workshop-builder.lock.yml`, `.github/workflows/workshop-order-review.lock.yml`; signature: `Upload activation artifact`; runs: 5; representative: https://github.com/githubnext/gh-aw-workshop/actions/runs/33952592026; confidence: medium.
- P1 — `github/gh-aw`; workflows: `.github/workflows/auto-triage-issues.lock.yml`, `.github/workflows/daily-evals-report.lock.yml`, `.github/workflows/sub-issue-closer.lock.yml`; signature: `Execute Codex CLI`; runs: 3; representative: https://github.com/github/gh-aw/actions/runs/33952319670; confidence: low.
- P2 — `githubnext/gh-aw-cao`; workflows: `.github/workflows/eu-cra-compliance-article-14-reporting-readiness.lock.yml`, `.github/workflows/eu-cra-compliance-scope-classifier.lock.yml`; signature: `Check workflow lock file`; runs: 2; representative: https://github.com/githubnext/gh-aw-cao/actions/runs/33953742823; confidence: low.
### Control Plane
- Correlation ID: `33955082331-209`
- Central repository: `githubnext/gh-aw-cao`
- Control-plane run: https://github.com/githubnext/gh-aw-cao/actions/runs/33955082331
> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33955259789) · pi · gpt54 · 23.3 AIC · ⌖ 8.64 AIC · ⊞ 8.3K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Fself-care-open-source-failures%22&type=issues)
> - [x] expires on Sep 19, 2026, 8:31 AM UTC
Contributor guide
Research direction
Start with the listed .github/workflows/*.lock.yml files in githubnext/gh-aw-cao and the target-authority error from their pre_activation runs. Check the target default branch and the referenced cao.json configuration, then reproduce an affected workflow. Done means new runs pass pre_activation without the target-authority error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100