Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa Adatta ai principianti
  • Qualcosa non va?
#3,807 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
88/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation

Direzione di ricerca

Inizia da workshop/side-quest-11-05-event-triggers.md e confronta i suoi riferimenti con workshop/07-your-first-workflow.md, workshop/14b-pr-reviewer-workflow.md e workshop/15-conditional-logic.md. Correggi il nome del file, i riferimenti ai passaggi, la tabella di confronto e il link conclusivo in modo che ciascuno punti al workflow descritto. Il lavoro è completato quando tutti i file referenziati, le etichette dei passaggi, i trigger e le descrizioni dei workflow corrispondono al contenuto del workshop.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
JavaScript
Stelle
49
Fork
20
Merge medio
7h 55m
PR unite (30g)
30

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/gh-aw-workshop

Tutte le issue di githubnext/gh-aw-workshop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.