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

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

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown, yaml
Domain
content, documentation

Research direction

Read workshop/04-github-actions-intro.md, focusing on the “Label a sample workflow” and “Why This Matters for Agentic Workflows” sections, then compare them with the annotated example above. Remove the repeated YAML from the exercise and shorten the comparison table as specified, keeping the named sections unchanged. Run markdownlint-cli2; the exercise should still ask learners to label the five lines, and the table should retain only Trigger and Steps.

Written by the indexing model from the issue text.

Description

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
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.