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

[workshop-sync] workshop/side-quest-11-05-event-triggers.md: wrong filename and mismatched Step 15/11c PR-reviewer references

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

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start with workshop/side-quest-11-05-event-triggers.md and compare its references against workshop/07-your-first-workflow.md, workshop/14b-pr-reviewer-workflow.md, and workshop/15-conditional-logic.md. Correct the filename, step references, comparison table, and closing link so each points to the described workflow. Done means all referenced files, step labels, triggers, and workflow descriptions match the workshop content.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-11-05-event-triggers.md

Problem

This file has several cross-reference and filename inaccuracies:

  1. It references the Step 7 workflow file as daily-status.md:

    You have an existing workflow file from Step 7 or Step 15, such as .github/workflows/daily-status.md.

    But workshop/07-your-first-workflow.md (Step 7) instructs learners to create .github/workflows/daily-report-status.md (compiling to daily-report-status.lock.yml), not daily-status.md.

  2. It references a non-existent step:

    This is a good fit when you want feedback tied to the current PR, like the PR Code Reviewer in Step 11c.

    No step "11c" exists in this workshop — side quests under the "11" series are numbered 11-01 through 11-09 (e.g. side-quest-11-04, side-quest-11-05). The actual PR reviewer workflow is built in 14b-pr-reviewer-workflow.md.

  3. It mislabels Step 15 as a PR reviewer step:

    The Daily Repo Status workflow in Step 7 and the PR Code Reviewer in Step 15 use the same workflow format...
    | 15 PR Code Reviewer | pull_request: {} | You want feedback only when a PR changes | add-comment |
    Return to the main adventure: Build — PR Code Reviewer.

    workshop/15-conditional-logic.md is titled "Make Your Workflow Smarter with Conditional Logic" and adds a shell-based conditional check to the schedule-triggered daily-status workflow from Step 7 — it does not use a pull_request trigger and is not a PR reviewer build step.

Current correct information

  • workshop/07-your-first-workflow.md creates daily-report-status.md / daily-report-status.lock.yml.
  • workshop/14b-pr-reviewer-workflow.md is the actual "Build a PR Reviewer" workflow step.
  • workshop/15-conditional-logic.md covers conditional logic for the daily-status/report workflow, not PR review.

Suggested fix

  1. Replace .github/workflows/daily-status.md with .github/workflows/daily-report-status.md.
  2. Replace "PR Code Reviewer in Step 11c" with a correct reference to 14b-pr-reviewer-workflow.md.
  3. Correct the "Step 7 vs Step 15" comparison section and table row so Step 15 is described accurately as conditional logic on the daily-status workflow (not a PR reviewer step with a pull_request trigger), or swap in 14b-pr-reviewer-workflow.md as the actual PR reviewer comparison target.
  4. Update the closing "Build — PR Code Reviewer" link/label to point to 14b-pr-reviewer-workflow.md, or relabel it to accurately describe 15-conditional-logic.md.

[!WARNING]

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • githubnext.github.io

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "githubnext.github.io"

See Network Configuration for more information.

Generated by 🔍 Workshop Sync Check · copilot · auto · 145.7 AIC · ⌖ 5.5 AIC · ⊞ 8.2K · ◷

  • expires on Sep 26, 2026, 4:57 AM UTC
Dominant language
JavaScript
Stars
49
Forks
20
Avg merge
7h 29m
Merged PRs (30d)
35

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.