[aw] Matt Pocock Skills Reviewer had a request rejected
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- github, github-actions, typescript
- Área
- ai-infra-agents, ci-cd, devops
Línea de trabajo
Start with the linked workflow file at .github/workflows/mattpocock-skills-reviewer.md on branch pelikhan-upgrade-engine-clis, then inspect the failed run and its model catalog for the unsupported model request. The issue suggests checking workflow frontmatter and Copilot model access or policy. Done means identifying the cause and fixing the workflow or documenting the applicable access issue; the payload does not identify a test.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Workflow Failure
Workflow: Matt Pocock Skills Reviewer
Branch: pelikhan-upgrade-engine-clis
Run: https://github.com/githubnext/rig/actions/runs/39142838035
Pull Request: #672
[!WARNING]
Model Not Supported: The requested model was rejected by the provider for this request.
This may be an invalid model name, a policy or access restriction for this token/repository, or a change in provider availability. Retrying the same session will not resolve a model that remains unavailable.
How to fix this
Specify a valid model for the selected engine in the workflow frontmatter:
---
engine: copilot
model: gpt-5-mini
---
To find valid models, check your engine/provider documentation (for Copilot see supported models) and the model catalog returned for the failing token/context.
If the model previously worked with the same workflow and token type, compare the successful and failing runs' model catalogs and request context. If the catalog changed, share sanitized timestamps, repository/organization context, and Copilot service request IDs with the Copilot model-access support team. Do not share tokens.
If the error text is No model available. Check policy enablement under GitHub Settings > Copilot, the model is not disabled in the workflow but by Copilot policy. Enable the model under GitHub Settings > Copilot > Policies for the org/repo, or pick a model that is already enabled. This can also be triggered by a subagent (task tool) dispatch requesting a model that the policy does not allow, even when the main agent's model is enabled.
[!WARNING]
Task Could Not Be Completed: The workflow recorded areport_incompletesignal: the task was not completed or completion could not be confirmed.
Error details:
Failure classification: request_rejection
Driver exit code: 1. The engine driver exited before a terminal safe output was recorded.
Last tool call status: not recorded
Failed tool calls observed: 0
Token budget state: unknown (no exhaustion signal recorded)
Step budget state (LLM invocations): unknown (no exhaustion signal recorded)
Safe-output tools: available at gateway snapshot (registered 8 tools)
Safe-output CLI calls observed: unknown (not recorded)
Safe-output MCP calls observed: 0
Safe-output persistence: not recorded
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Engine error: Requested model is not supported (model_not_supported_error)
Engine HTTP error codes: 400
Last engine error type: model_not_supported_error
Retry attempts observed: 0
A comment or other safe output does not confirm that the requested task was completed. Only inferred runtime status and error codes are reported; agent text is excluded.
Failure Diagnostics
Agent job: agent
Agent job conclusion: failure
Failing step: Execute GitHub Copilot CLI
The runtime did not record a specific cause. Check the linked run for failure details.
Only runtime metadata is shown; agent-generated text is excluded.
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/rig/actions/runs/39142838035
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 mattpocock-skills-reviewer failure in https://github.com/githubnext/rig/actions/runs/39142838035
[!TIP]
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter:safe-outputs: report-failure-as-issue: false
Generated from Matt Pocock Skills Reviewer · ◷
- expires on Oct 25, 2026, 4:02 PM UTC
- Lenguaje dominante
- TypeScript
- Estrellas
- 14
- Forks
- 0
- Merge medio
- 9 h 49 min
- PR fusionados (30 d)
- 32
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de githubnext/rig
-
agentic-workflows
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
githubnext/rig#676 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 48/100
githubnext/rig#675 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
githubnext/rig#674 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
githubnext/rig#671 ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 5/5 Más de una semana Aptitud para principiantes 1/100
githubnext/rig#670 ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/rig
Issues similares
-
Admin search throws for permissions added through Admin.generalIndexItems('permissions', ...)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Koenkk/zigbee-herdsman-converters#13540 ·
Los mantenedores suelen responder en 1 día
-
Add: Tequila Music TV RO SDAbiertocheck:passed streams:add
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
iptv-org/iptv#55821 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/busola/ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
kyma-project/busola#5442 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel-labs/wterm#246 ·
Los mantenedores suelen responder en 1 día