Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[aw] Matt Pocock Skills Reviewer had a request rejected

Ouverte
  • Quelque chose ne va pas ?
#608 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
40/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
github-actions, markdown, yaml
Domaine
ci-cd

Piste de recherche

The failing workflow is .github/workflows/mattpocock-skills-reviewer.md; its frontmatter sets the engine and model, and the rejected model name is the thing to change. Check the linked run to confirm which model was requested, then pick one that is enabled for the repository's Copilot policy. Done when the workflow runs without a model_not_supported_error and the run completes a review or reports a real outcome.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

agentic-workflows
Workflow Failure

Workflow: Matt Pocock Skills Reviewer
Branch: rig-tasks/2026-10-09-55a92e3b0cd901fe
Run: https://github.com/githubnext/rig/actions/runs/38026838226

[!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 agent reported that the task could not be performed due to an infrastructure or tool failure.

Error details: 
engine_driver_failure
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Driver exit code: 1. The engine driver exited before a terminal safe output was recorded.
Engine error: Requested model is not supported (model_not_supported_error)
Failure classification: request_rejection
Last engine error type: model_not_supported_error
Retry attempts observed: 0

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

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/38026838226
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

[!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: false

Generated from Matt Pocock Skills Reviewer · ◷

  • expires on Oct 17, 2026, 5:19 AM UTC
Langage dominant
TypeScript
Étoiles
14
Forks
0
Merge moyen
3 h 38 min
PR mergées (30 j)
29

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/rig

Toutes les issues de githubnext/rig

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.