[aw] Matt Pocock Skills Reviewer had a request rejected
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 40/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github-actions, markdown, yaml
- 領域
- ci-cd
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.
- 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/38026838226
[!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 17, 2026, 5:19 AM UTC
- 主要語言
- TypeScript
- 星號
- 13
- 分支
- 0
- 平均合併
- 3 小時 44 分鐘
- 30 天內合併 PR
- 28
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
githubnext/rig 的其他 Issue
-
agentic-workflows
難度 1/5 1 小時以內 新手友好度 48/100
githubnext/rig#634 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 4/5 3-5 天 新手友好度 35/100
githubnext/rig#633 · 1 則留言 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 4/5 3-5 天 新手友好度 30/100
githubnext/rig#631 ·
維護者通常 1 天內回覆
-
ai-agent automation
難度 5/5 一週以上 新手友好度 1/100
githubnext/rig#630 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 3/5 1-2 天 新手友好度 45/100
githubnext/rig#629 ·
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
db-ux-design-system/core-web#8461 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
Cannot run an integration on windows when power shell is selected as the default profile terminal未關閉Priority/Blocker Type/Bug
難度 2/5 1-3 小時 新手友好度 76/100
wso2/product-integrator#2767 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 85/100
-
severity:low
難度 1/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆