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

[awf-feature-surfacing] Surface model-routing and governance toolset guidance

已关闭 适合新手
  • 哪里不对？
#68,542 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
68/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions
领域
documentation

调研方向

从 .github/aw/syntax-engine.md 第 97 行的过时表述开始，并与 docs/src/content/docs/reference/model-routing.md 对照检查，后者已经写明了正确的规则。然后在 docs/src/content/docs/reference/github-tools.md 第 22 行的 Available 列表中添加治理信息，工具用途和 token 权限使用 pkg/workflow/data/github_toolsets_permissions.json。当两个页面都与 schema 及该权限映射一致时，即为完成。

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

描述

automation awf compiler specifications
Overview

The seven-day AWF spec/compiler review found two user-facing guidance gaps in recently changed capabilities. The compiler and schema accept the behavior, but two discoverable syntax references still give incomplete or incorrect instructions.

Key findings
  • P2 — Model routing syntax: .github/aw/syntax-engine.md says engine.model-routing.allowed-models is required and implies it limits models the routed task may call. Since #68495, it is an optional router candidate list (AWF v0.28.33+); only models.allowed and models.blocked set the request policy. The same syntax entry omits the engine.model-provider: github requirement for routed Claude and Codex workflows enforced by #68080.
  • P2 — GitHub governance toolset: The tools.github.toolsets schema accepts governance after #67738, and .github/aw/syntax-tools-imports.md lists it, but the Available list in docs/src/content/docs/reference/github-tools.md omits it. The reference also lacks a short explanation of its custom property and ruleset tools and token permissions.
Evidence and current surfacing
  • pkg/parser/schemas/main_workflow_schema.json has engine.model-routing required fields goal and mode only, and describes allowed-models as optional router candidates. It includes governance in github_toolset_name.
  • pkg/workflow/model_routing.go applies routing policy and provider validation; pkg/workflow/data/github_toolsets_permissions.json maps governance to custom property and ruleset tools and their permission needs.
  • docs/src/content/docs/reference/model-routing.md correctly explains optional candidates, the AWF version boundary, request policy, and the GitHub provider requirement. docs/src/content/docs/reference/frontmatter.md also describes the candidate/policy distinction.
  • .github/aw/syntax-engine.md:97 retains the stale required-field and request-limit wording. docs/src/content/docs/reference/github-tools.md:22 has the incomplete toolset list.
  • Relevant changes: #68495 (63e2c65) and #68080 (70f8448) for routing; #67738 for GitHub MCP toolsets.
Next actions
  • P2: Update .github/aw/syntax-engine.md to call allowed-models optional for AWF v0.28.33+, describe it as router candidates only, and point readers to models.allowed / models.blocked for request policy. State that routed Claude and Codex must resolve engine.model-provider to github.
  • P2: Update the GitHub tools reference's available-toolsets list and add a compact governance example with the tool purposes and required token permissions, using the permission map as the source.

Generated by 🧭 Daily AWF Spec Compiler Surfacing Review · codex · gpt60 · 127.8 AIC · ⌖ 5.96 AIC · ⊞ 14.1K · ◷

  • expires on Oct 20, 2026, 2:27 PM UTC-08:00
主要语言
Go
星标
5.4k
派生
584
平均合并
3 小时 59 分钟
30 天内合并 PR
823

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

github/gh-aw 的其他 Issue

查看 github/gh-aw 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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