githubnext / githubnext/ado-aw
[aw] Issue Triage failed
- Dominant language
- Rust
- Stars
- 23
- Forks
- 8
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 22
Description
### Workflow Failure
**Workflow:** [Issue Triage](https://github.com/githubnext/ado-aw/blob/main/.github/workflows/issue-triage.md)
**Branch:** main
**Run:** https://github.com/githubnext/ado-aw/actions/runs/34377019286
> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.
**Last agent output:**
```
✗ test safeoutputs on new shellId (shell)
│ safeoutputs --help
└ Permission denied and could not request permission from user
✗ dump copilot json configs (shell)
│ find /home/runner/.copilot -iname "*.json" -exec sh -c 'echo ==={}===; cat {}' \; 2>&1 | head
│ -200
└ Permission denied and could not request permission from user
/ Search (glob)
│ "**/allowed*"" in ~/.copilot
└ No matches found
```
### 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/ado-aw/actions/runs/34377019286
````
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 issue-triage failure in https://github.com/githubnext/ado-aw/actions/runs/34377019286`
> [!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 [Issue Triage](https://github.com/githubnext/ado-aw/actions/runs/34377019286) · 156.6 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fado-aw+is%3Aissue+%22gh-aw-workflow-id%3A+issue-triage%22&type=issues)
> - [x] expires on Sep 16, 2026, 4:43 PM UTC
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/issue-triage.md and the linked workflow run. Review the failed copilot engine output, especially the safeoutputs and shell permission errors, then use debug.md or the agentic-workflows skill as directed. Done means the Issue Triage workflow completes successfully without the reported engine failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100