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/35019671236
> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.
**Missing Data:**
- **GitHub repository evidence for candidate ranking and bounded discovery**: Stopped additional GitHub API/model work after hitting installation API rate limits and repeated gh runtime thread-creation failures while inspecting candidate repositories beyond initial metadata. Per control instructions, no further API work was performe
\[Content truncated due to length\]
- *Context*: orchestrator run 35019671236 correlation 35019671236-303 for githubnext/gh-aw-cao package software-development-practices
- *Alternatives*: Re-run this orchestrator with fresh API budget or provide precomputed repository-tree/workflow evidence in control-precompute so ranking can complete without extra API reads.
### 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/35019671236
````
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/35019671236`
> [!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/35019671236) · pi · 21.4 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 16, 2026, 8:31 PM UTC
Contributor guide
Research direction
Start with the Dev Practices workflow at .github/workflows/software-development-practices.md and inspect run 35019671236 alongside debug.md. Reproduce or trace the missing repository evidence, installation API rate limits, and gh runtime thread-creation failures; done means the workflow completes with the required data or clearly handles the failure.
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
- 42/100