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

[workshop-sync] side-quest-11-01b-workflow-structure.md: inconsistent step number (Step 7 vs Step 11)

Closed Beginner friendly
#4,856 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
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Open workshop/side-quest-11-01b-workflow-structure.md and compare the Step 11 reference in the intro with the Step 7 wording around line 24. Check side-quest-10-01-agent-brief.md and 07-your-first-workflow.md to confirm the intended numbering. Update the inconsistent reference, then verify the page uses the same step number or links to the workflow page.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-11-01b-workflow-structure.md

Problem

The intro (line 5) says:

read this before building Step 11

but line 24 says:

The five frontmatter sections you'll build in Step 7:

The rest of the workshop (e.g. side-quest-10-01-agent-brief.md) calls the page that builds this workflow (07-your-first-workflow.md) Step 11, so the file contradicts itself.

Suggested fix

Change "Step 7" to "Step 11" on line 24 (or better, link to 07-your-first-workflow.md without a hard-coded step number).

Generated by 🔍 Workshop Sync Check · copilot · auto · 54.7 AIC · ⌖ 0.55 AIC · ⊞ 9.3K · ◷

  • expires on Oct 23, 2026, 2:47 AM UTC
Dominant language
JavaScript
Stars
55
Forks
36
Avg merge
2d 8h
Merged PRs (30d)
17

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.