githubnext / githubnext/gh-aw-cao
[self-care:open-source-failures] AI credit optimizer blocked at GitHub App token generation
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
`githubnext/gh-aw-cao`'s AI credit optimizer failed five times in the last seven days at the same early step, `Generate GitHub App token`, so the workflow never reached analysis. This is the next highest-severity untracked cluster with an actionable repeated signature in the bounded snapshot.
**Action:** CAO maintainers should restore the optimizer's GitHub App credential path and prove the workflow can complete at least one end-to-end run; accept when a fresh `AW Optimization / AI Credit Savings` run succeeds past token generation and no new `Generate GitHub App token` failures appear in the next snapshot.
Assign to Copilot.
Agent prompt
Investigate repeated `Generate GitHub App token` failures in `githubnext/gh-aw-cao` workflow `.github/workflows/optimization-ai-credit-optimizer.lock.yml` and implement the smallest safe fix.
Tasks:
1. Trace how the workflow obtains the GitHub App credentials used at token generation.
2. Identify whether the failure is caused by missing inputs, wrong app configuration, permissions mismatch, or recent workflow/source drift.
3. Fix the workflow or its validated inputs without broadening permissions.
4. Add or update tests or validation so future misconfiguration fails with a clearer diagnostic before repeated scheduled failures.
5. Regenerate any required workflow artifacts.
Return the root cause, changed files, and the exact acceptance evidence.
Critical findings:
- Representative run: https://github.com/githubnext/gh-aw-cao/actions/runs/33929404817
- Corroborating runs: https://github.com/githubnext/gh-aw-cao/actions/runs/33929378228, https://github.com/githubnext/gh-aw-cao/actions/runs/33929350517, https://github.com/githubnext/gh-aw-cao/actions/runs/33929323165, https://github.com/githubnext/gh-aw-cao/actions/runs/33929296063
- Severity: P1
- Runs in cluster: 5
- Evidence-supported cause: the optimizer workflow is blocked before analysis because GitHub App token generation is failing
- Confidence: medium
Bounded evidence
Affected workflow:
- `.github/workflows/optimization-ai-credit-optimizer.lock.yml`
Repeated signature in the snapshot:
- failure job: `agent`
- failure step: `Generate GitHub App token`
The snapshot is truncated to the newest 100 failed runs, so additional older occurrences may exist outside this bounded evidence.
### Control Plane
- Correlation ID: `33936079722-192`
- Central repository: `githubnext/gh-aw-cao`
- Control plane run: `https://github.com/githubnext/gh-aw-cao/actions/runs/33936079722`
> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33936275524) · pi · gpt54 · 34.9 AIC · ⌖ 8.65 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, 1:34 AM UTC
Contributor guide
Research direction
Start with .github/workflows/optimization-ai-credit-optimizer.lock.yml and the representative Actions run, focusing on the agent job's “Generate GitHub App token” step. Trace the credential inputs and validated permissions, then use the listed corroborating runs to confirm the repeated failure. Done means a fresh AW Optimization / AI Credit Savings run passes token generation and the next snapshot has no new failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100