githubnext / githubnext/gh-aw-cao
[aw] Dev Practices is missing required data
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Workflow Failure
**Workflow:** [Dev Practices](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/software-development-practices.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/34551317446
> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.
**Missing Data:**
- **github\_api\_evidence**: GitHub API rate limit exceeded while collecting repository metadata needed to rank candidates and decide worker dispatches. Policy requires stopping additional API and model work rather than retrying or reducing scope silently.
- *Context*: Control role: orchestrator. Initial evidence collected only for github/gh-aw before rate limit. Unresolved work: complete bounded ranking across precomputed candidates, select up to 7 repositories, and dispatch eligible software-development-practices worke
\[Content truncated due to length\]
- *Alternatives*: Re-run this orchestrator later or manually with refreshed API budget; preserve precomputed batch and correlation id 34551317446-188.
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/gh-aw-cao/actions/runs/34551317446
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow software-development-practices failure in https://github.com/githubnext/gh-aw-cao/actions/runs/34551317446`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [Dev Practices](https://github.com/githubnext/gh-aw-cao/actions/runs/34551317446) · pi · 5.97 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+software-development-practices%22&type=issues)
> - [x] expires on Sep 18, 2026, 1:40 AM UTC
Contributor guide
Research direction
Start with the failed run and read .github/workflows/software-development-practices.md, then follow the debugging guidance in debug.md and the agentic-workflows skill. Investigate the reported github_api_evidence rate-limit failure and verify the workflow can complete its bounded ranking and dispatch work without reporting missing data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100