[aw] Matt Pocock Skills Reviewer had a request rejected
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, typescript
调研方向
Start with the linked workflow file, .github/workflows/mattpocock-skills-reviewer.md, and inspect its engine and model frontmatter. Then read the linked failed run and follow the issue’s suggested debug.md and agentic-workflows skill to identify why the requested model was rejected. Done means the workflow uses a supported, available model and the agent task completes successfully.
由索引模型根据 Issue 内容生成。
描述
Workflow Failure
Workflow: Matt Pocock Skills Reviewer
Branch: pelikhan-pi-dependency-upgrade
Run: https://github.com/githubnext/rig/actions/runs/38335638601
[!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/38335638601
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/38335638601
[!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 20, 2026, 2:14 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 天 新手友好度 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 天内回复
-
agentic-workflows
难度 3/5 1-2 天 新手友好度 48/100
githubnext/rig#628 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
better-auth/better-auth#11723 · 1 个 reaction ·
维护者通常 1 天内回复
-
area: docs difficulty: easy documentation good first issue
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Worker-Erstellung bricht langsame Git-Worktree-Checkouts nach 20 Sekunden ab可能已有人在做 @KajoVanBuyten 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 69/100
AgentSystemLabs/agent-office#367 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
pierrecomputer/pierre#1187 ·
维护者通常 1 天内回复
-
area: frontend bug
难度 1/5 1-3 小时 新手友好度 85/100
snapotter-hq/SnapOtter#2425 ·
维护者通常 1 天内回复