[workshop-sync] workshop/17-add-mcp-tools.md: missing safe-outputs create-issue block for issue-posting example
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 88/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github, markdown
调研方向
从 workshop/17-add-mcp-tools.md 开始，将其中的示例与 workshop/07-your-first-workflow.md 中的 safe-outputs 模式及链接的 Frontmatter 参考进行比较。更新示例 Frontmatter 和对应的 /agentic-workflows prompt，使 create-issue 块存在，然后确认 task brief 中发布 issue 的说明与所示配置一致。
由索引模型根据 Issue 内容生成。
描述
Workshop file reviewed
workshop/17-add-mcp-tools.md
Problem
The task brief the workshop tells learners to send to Copilot CLI explicitly asks the agent to write a GitHub issue:
/agentic-workflows update .github/workflows/daily-status.md to add atools:block ... and update the task brief to tell the agent to use GitHub tools to fetch the last 5 commits and all open issues labelledbug, then write a daily summary and post it as a new issue.
And later:
Post the summary as a new issue titled "Daily Status — {today's date}".
However, the example frontmatter shown in the file only includes:
permissions:
contents: read
tools:
github:
mode: gh-proxy
toolsets: [default]
There is no safe-outputs: create-issue: block. Per gh-aw's frontmatter reference, write permissions are not allowed on the job token — agents must use safe-outputs for any write operation such as creating an issue. Without a safe-outputs.create-issue entry, the workflow shown has no permitted mechanism to actually post the issue the task brief asks for, so following the file as written would either fail at runtime or silently produce no issue.
Current correct syntax
The gh-aw reference docs (and the workshop's own step 07, workshop/07-your-first-workflow.md) show the correct pattern: pair tools.github.mode: gh-proxy with a safe-outputs.create-issue: block, e.g.:
permissions:
contents: read
tools:
github:
mode: gh-proxy
toolsets: [default]
safe-outputs:
create-issue:
See Frontmatter Reference and Safe Outputs Reference: "Write permissions are not allowed for security reasons; use safe-outputs for write operations instead."
Suggested fix
Add a safe-outputs:\n create-issue: block to both the example tools: frontmatter shown in "Add an MCP server to your workflow" and the corresponding /agentic-workflows prompt text, so the example matches what's actually required to post a new issue, consistent with the pattern already used in workshop/07-your-first-workflow.md.
Generated by 🔍 Workshop Sync Check · copilot · auto · 153.2 AIC · ⌖ 7.13 AIC · ⊞ 8.2K · ◷
- expires on Sep 29, 2026, 5:07 AM UTC
- 主要语言
- JavaScript
- 星标
- 51
- 派生
- 23
- 平均合并
- 8 小时 37 分钟
- 30 天内合并 PR
- 23
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/gh-aw-workshop 的其他 Issue
-
feedback simulation workshop
难度 1/5 1 小时以内 新手友好度 85/100
githubnext/gh-aw-workshop#4007 ·
维护者通常 1 天内回复
-
documentation guidelines
难度 1/5 1 小时以内 新手友好度 92/100
githubnext/gh-aw-workshop#4003 ·
维护者通常 1 天内回复
-
documentation guidelines
难度 1/5 1 小时以内 新手友好度 92/100
githubnext/gh-aw-workshop#4002 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 95/100
githubnext/gh-aw-workshop#3986 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 75/100
githubnext/gh-aw-workshop#3980 ·
维护者通常 1 天内回复
查看 githubnext/gh-aw-workshop 的全部 Issue
相似的 Issue
-
documentation good first issue help wanted
难度 1/5 1-3 小时 新手友好度 92/100
维护者通常 1 天内回复
-
automated issue report
难度 1/5 1 小时以内 新手友好度 85/100
lirantal/discoprint#29 ·
维护者通常 1 天内回复
-
feature-request
难度 2/5 1-3 小时 新手友好度 68/100
louislam/uptime-kuma#7914 · 1 条评论 ·
维护者通常 1 天内回复
-
Code Cleanup dependencies
难度 1/5 1 小时以内 新手友好度 68/100
ProjectSidewalk/SidewalkWebpage#5609 ·
维护者通常 1 天内回复
-
help wanted javascript
难度 2/5 1-3 小时 新手友好度 68/100
OWASP/cornucopia#3538 ·
维护者通常 1 天内回复