[workflow-editor] Fix stale heading references to workshop-author.md validation procedure
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 78/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions
- 领域
- ci-cd
调研方向
检查 .github/workflows/side-quest.md、security-side-quest.md 和 workshop-skill-activity-author.md 中的引用,然后将它们与 workshop-author.md 中未编号的标题进行比较。更新过时的标题引用,并运行 gh aw compile --validate 以重新生成匹配的 lock 文件。当三个 workflow 文件都指向现有 procedure 且验证成功时,即表示完成。
由索引模型根据 Issue 内容生成。
描述
[!CAUTION]
Protected files were modified in this change.
This pull request is inrequest_reviewmode and requires explicit human scrutiny before merge.Protected files:
.github/workflows/security-side-quest.lock.yml,.github/workflows/security-side-quest.md,.github/workflows/side-quest.lock.yml,.github/workflows/side-quest.md,.github/workflows/workshop-skill-activity-author.lock.yml,.github/workflows/workshop-skill-activity-author.md
Removes a small piece of stale duplication/bloat: three workflow files pointed to a numbered subsection heading (### 5. Validate agentic workflow snippets) in workshop-author.md that no longer exists — the actual heading is ### Validate agentic workflow snippets (unnumbered, per the "don't number headers" guideline).
Files changed:
.github/workflows/side-quest.md.github/workflows/security-side-quest.md.github/workflows/workshop-skill-activity-author.md- Regenerated matching
*.lock.ymlfiles viagh aw compile --validate
Why this is more Skills-like: shared instructions should point learners (and agents) to a procedure that's easy to find. A stale anchor forces the reader to search instead of following a direct pointer — the opposite of the short, direct guidance this workshop aims for. This fix keeps the "read the shared procedure" pattern intact while making the reference accurate again.
[!WARNING]
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.github.com[!TIP]
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:tools: github: mode: gh-proxySee GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:network: allowed: - defaults - "api.github.com"See Network Configuration for more information.
Generated by ✂️ Workflow Skills Editor · copilot · auto · 43.8 AIC · ⌖ 7.82 AIC · ⊞ 7.5K · ◷
- expires on Sep 30, 2026, 7:43 AM UTC
[!NOTE]
This was originally intended as a pull request, but the git push operation failed.Original error: The process '/usr/bin/git' failed with exit code 1
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.
Create the pull request manually
# Download the artifact from the workflow run
gh run download '36537846522' -n agent -D '/tmp/agent-36537846522'
# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-36537846522/aw-fix-workflow-author-snippet-ref.bundle'
temp_ref='refs/bundles/create-pr-fix-workflow-author-snippet-ref-94e43af149fbe638-31361a0e'
target_ref='refs/heads/fix/workflow-author-snippet-ref-94e43af149fbe638'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'fix/workflow-author-snippet-ref-94e43af149fbe638'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"
# Push the branch to the target remote
git push 'origin' 'fix/workflow-author-snippet-ref-94e43af149fbe638'
# Create the pull request
gh pr create --title '[workflow-editor] Fix stale heading references to workshop-author.md validation procedure' --base 'main' --head 'fix/workflow-author-snippet-ref-94e43af149fbe638' --repo 'githubnext/gh-aw-workshop'
- 主要语言
- JavaScript
- 星标
- 55
- 派生
- 36
- 平均合并
- 2 天 8 小时
- 30 天内合并 PR
- 17
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
githubnext/gh-aw-workshop 的其他 Issue
-
[workshop-sim] Improve: Strengthen practice and checkpoints in Step 05 (What Are Agentic Workflows?)未关闭feedback simulation workshop
难度 2/5 1-3 小时 新手友好度 85/100
githubnext/gh-aw-workshop#4972 ·
维护者通常 1 天内回复
-
feedback simulation workshop
难度 2/5 1-3 小时 新手友好度 70/100
githubnext/gh-aw-workshop#4971 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 85/100
githubnext/gh-aw-workshop#4969 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 半天 新手友好度 85/100
githubnext/gh-aw-workshop#4966 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 75/100
githubnext/gh-aw-workshop#4964 ·
维护者通常 1 天内回复
查看 githubnext/gh-aw-workshop 的全部 Issue
相似的 Issue
-
bug require-triage
难度 2/5 1-3 小时 新手友好度 72/100
expressjs/expressjs.com#2549 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
vercel-labs/agent-skills#348 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
NanmiCoder/dsh-agent-teams#289 ·
维护者通常 1 天内回复