Repository navigation
Closed as not planned
Labels
Description
Workflow Failure
Workflow: LintMonster
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/28176350850
Warning
Agent Assignment Failed: Failed to assign agent to issues or pull requests.
Assignment Errors:
- Issue Standardize CLI help section order and GHE note wording #41461 (agent: copilot): copilot coding agent is not available for this repository
- Issue Update existing MCP configs with required gh-aw server fields #41462 (agent: copilot): copilot coding agent is not available for this repository
- Issue Reduce
sandbox.agent.sudo: falseusage to policy target across agentic workflows #41463 (agent: copilot): copilot coding agent is not available for this repository
To resolve this, verify the agent token and Copilot access configuration:
- Configure a valid
GH_AW_AGENT_TOKENas a fine-grained PAT with Agent tasks: read and write permission (GitHub App installation tokens are not supported) - Ensure Copilot coding agent is enabled for this repository and a Copilot Business or Enterprise subscription is active
- Docs: https://github.github.com/gh-aw/reference/copilot-cloud-agent/#authentication
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/github/gh-aw/actions/runs/28176350850
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow lint-monster failure in https://github.com/github/gh-aw/actions/runs/28176350850
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:
safe-outputs:
report-failure-as-issue: falseGenerated from LintMonster · 65.3 AIC · ◷
- expires on Jun 26, 2026, 2:20 AM UTC
Activity
github-actions commentedon Jun 26, 2026
This issue was automatically closed because it expired on 2026-06-26T02:20:07.674Z.