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

[curriculum-eval] 04-github-actions-intro.md: cognitive_load — redundant YAML example doubles concept count in labeling exercise

Aperta Adatta ai principianti
  • Qualcosa non va?
#4,489 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

Leggi workshop/04-github-actions-intro.md, concentrandoti sulle sezioni “Label a sample workflow” e “Why This Matters for Agentic Workflows”, poi confrontale con l’esempio annotato qui sopra. Rimuovi lo YAML ripetuto dall’esercizio e accorcia la tabella di confronto come specificato, lasciando invariate le sezioni indicate. Esegui markdownlint-cli2; l’esercizio deve continuare a chiedere agli studenti di etichettare le cinque righe e la tabella deve contenere solo Trigger e Steps.

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

Descrizione

curriculum documentation quality

File: workshop/04-github-actions-intro.md
Overall Score: 5.39 / 10.0 (corpus mean: 6.09)

Flagged Dimensions:

Dimension Score Benchmark Delta
cognitive_load 6.8 ≤ 15 new concepts −6.5 concept penalty (28 new concepts, nearly double budget, in only 756 words)
active_learning 3.9 density ≥ 3 −6.1 (density 1.19)

Root Cause (≤ 2 sentences):
This is the corpus's highest new-concept-per-word page outside the anthropic-key side quest — 28 bolded/code terms in 756 words — because it simultaneously introduces Actions vocabulary (trigger, job, runner, step, action), a full annotated YAML example, a second "label the five parts" exercise with its own five-line YAML, and an Actions-vs-agentic comparison table, each contributing new terms in quick succession. The "Label a sample workflow" exercise repeats four of the five terms already defined in the "Quick Refresher" section and annotated example just above it, adding redundant vocabulary load rather than new content.

Evidence (quoted from the file):

"on: [push] / jobs: test: ... Write a label beside each line: 1. on: [push] 2. test: (the job name under jobs:) 3. runs-on: ubuntu-latest 4. uses: actions/checkout@v4 5. run: echo \"All checks passed\"" (a second full YAML example restating trigger/job/runner/step/action after they were already defined and shown in the first annotated example)

Learning Science Rationale:
Cognitive Load Theory's redundancy effect states that presenting the same information in two different forms (an annotated code block, then a nearly identical un-annotated code block for labeling) increases extraneous load without adding germane learning value, because learners must reprocess information they already encoded. Removing the duplicate "Hello Workflow" YAML in the labeling exercise and instead asking learners to label the already-annotated example consolidates this page's concept count under budget while preserving the retrieval-practice benefit of the labeling activity.

Improvement Prompt (for an agent):

Edit workshop/04-github-actions-intro.md to reduce concept load:
1. In the "## Label a sample workflow" section, remove the second
   "```yaml .github/workflows/hello-workflow.yml``` on: [push] / jobs: test: ..."
   code block, since it duplicates the "Annotated example" code block above it almost
   term-for-term. Instead have the exercise instruction say "Using the annotated example
   above, write a label beside each of these five lines" and reference the five lines by
   quoting them inline rather than repeating the full YAML block.
2. Shorten the "Why This Matters for Agentic Workflows" comparison table to the 2 rows
   most relevant to this page (Trigger, Steps) and move the remaining rows (Runner,
   Output) to 05-agentic-workflows-intro.md where they are covered in more depth, to
   avoid introducing extra comparison vocabulary twice in one page.
Keep the "what is a runner?" <details> block, the "Try it" exercise, and the Checkpoint
section unchanged. Re-run markdownlint-cli2 after editing.

Expected Score After Fix: 6.3–6.7 / 10.0

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 119.1 AIC · ⌖ 17.8 AIC · ⊞ 10.4K · ◷

  • expires on Oct 13, 2026, 4:04 AM UTC
Lingua principale
JavaScript
Stelle
52
Fork
26
Merge medio
12h 58m
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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.