[workflow-editor] Fix stale heading references to workshop-author.md validation procedure
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Inspect the references in .github/workflows/side-quest.md, security-side-quest.md, and workshop-skill-activity-author.md, then compare them with the unnumbered heading in workshop-author.md. Update the stale heading references and run gh aw compile --validate to regenerate the matching lock files. Done means all three workflow files point to the existing procedure and validation succeeds.
Written by the indexing model from the issue text.
Description
[!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'
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 23
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 23
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
feedback simulation workshop
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4007 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#4003 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#4002 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
githubnext/gh-aw-workshop#3986 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#3980 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
新讀者走讀回報,照著一篇文章實際操作Opendocumentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lirantal/discoprint#29 ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
louislam/uptime-kuma#7914 · 1 comment ·
Maintainers usually reply within 1 day
-
Code Cleanup dependencies
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ProjectSidewalk/SidewalkWebpage#5609 ·
Maintainers usually reply within 1 day
-
help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OWASP/cornucopia#3538 ·
Maintainers usually reply within 1 day