Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[aw] Matt Pocock Skills Reviewer: has an unavailable configured model

未关闭
  • 哪里不对？
#697 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
57/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github, github-actions, typescript
领域
ai-infra-agents, ci-cd

调研方向

Start with .github/workflows/mattpocock-skills-reviewer.md on branch pelikhan-agentic-engine-upgrades and inspect the failed run’s model configuration and logs. Check which models are available to the agentic-workflows integration for that run context. Done means the workflow selects a supported model and a rerun completes; the issue does not identify the model currently configured or name a test.

由索引模型根据 Issue 内容生成。

描述

agentic-workflows
What happened

Matt Pocock Skills Reviewer has an unavailable configured model.

View run #39691205577 · Workflow source · Previous failures

Branch: pelikhan-agentic-engine-upgrades

Next step

Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.

Failure details

[!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.

Copilot also filters models by integration. A model enabled by organization policy and available in the standalone CLI can still be unavailable to the agentic-workflows integration. In particular, Gemini models have been absent from that integration's catalog. The bundled gh-aw model catalog is not proof of live access. Select a model offered to this workflow; enabling a missing model for agentic-workflows requires Copilot API support. Do not change the integration ID to bypass access policy.

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]
Engine Failure: The copilot engine terminated unexpectedly.

Error details: 
Driver exit code: 1

Review the workflow run logs for diagnostics. Raw agent output is omitted because it may contain secrets.

Copy a debugging prompt

Paste this into your coding agent:

Debug the agentic workflow "mattpocock-skills-reviewer" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/githubnext/rig/actions/runs/39691205577

If the repository includes the agentic-workflows skill, load it before investigating.

Manage failure notifications

To stop creating failure issues for this workflow, set this in its frontmatter and recompile:

safe-outputs:
  report-failure-as-issue: false

This only disables issue reporting; it does not fix the failure.

Generated from Matt Pocock Skills Reviewer · ◷

  • expires on Oct 28, 2026, 11:10 PM UTC
主要语言
TypeScript
星标
14
派生
0
平均合并
9 小时 27 分钟
30 天内合并 PR
34

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/rig 的其他 Issue

查看 githubnext/rig 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。