Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[workshop-sync] side-quest-12-01-iterate-agent-output.md: workflow name/file path mismatch with Steps 7-9

Closed Beginner friendly
  • Is something wrong?
#4,046 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown
Domain
documentation

Research direction

Start with workshop/side-quest-12-01-iterate-agent-output.md, then compare the workflow name and path against workshop/07-your-first-workflow.md and workshop/09-agentic-editing.md. Update the mismatched workflow name and file-path references, then search the side-quest file to confirm the incorrect values are gone and the canonical values remain.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-12-01-iterate-agent-output.md

Problem

This side quest's prerequisite is completing Step 9, which builds on the workflow created in Step 7. Steps 7–9 consistently name the workflow Daily Report Status and the source file .github/workflows/daily-report-status.md. This side quest file uses different names that don't match the learner's actual workflow:

  1. The example gh command references the wrong workflow name:

    RUN_ID=$(gh run list --workflow "Daily Repo Status" --limit 1 --json databaseId --jq '.[0].databaseId')

    The canonical workflow name: set in Step 7 is "Daily Report Status", not "Daily Repo Status." Running the example as written would return no results for a learner following the workshop in order.

  2. The prompt example and body-edit instructions reference the wrong file path:

    Using the agentic-workflows skill, update .github/workflows/daily-status.md
    If you have a terminal open, open \.github/workflows/daily-status.md` and edit the Markdown body directly`

    The file created in Steps 7–9 is .github/workflows/daily-report-status.md, not daily-status.md. The daily-status.md filename is only introduced later, in Step 15.

Current correct behaviour

Per workshop/07-your-first-workflow.md and workshop/09-agentic-editing.md, the workflow is named Daily Report Status and lives at .github/workflows/daily-report-status.md.

Suggested fix

  • Replace "Daily Repo Status" with "Daily Report Status" in the gh run list --workflow example.
  • Replace all occurrences of .github/workflows/daily-status.md with .github/workflows/daily-report-status.md in this file.

Generated by 🔍 Workshop Sync Check · copilot · auto · 204.5 AIC · ⌖ 6.8 AIC · ⊞ 9.2K · ◷

  • expires on Oct 2, 2026, 8:58 AM UTC
Dominant language
JavaScript
Stars
52
Forks
26
Avg merge
12h 58m
Merged PRs (30d)
15

Getting set up

Open in Codespaces

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.