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

[workshop-sync] workshop/23-ab-experiments.md: invalid \{\\{\#endif}} templating syntax and incorrect tie-break description

Open Beginner friendly
#4,531 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
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github, markdown
Domain
documentation

Research direction

Open workshop/23-ab-experiments.md and inspect the two conditional blocks and the variant selection explanation and checkpoint named in the issue. Compare the wording with the templating and A/B experiments references linked in the report. Done when both closing tags use the documented syntax and the text describes random tie breaking accurately.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/23-ab-experiments.md

Problem 1 — invalid templating syntax

The file uses {{#endif}} to close conditional template blocks, for example:

{{#if experiments.output_style }}
Write according to the output_style: ${{ experiments.output_style }}.
...
{{#endif}}

This appears twice. {{#endif}} is not valid gh-aw templating syntax and will not close the conditional block.

Problem 2 — incorrect tie-break description

The file states:

On each run, gh-aw picks the variant with the lowest invocation count so far (ties are broken by first-in-array order), then saves the updated counts and uploads them as the experiment artifact.

and the related checkpoint item:

You can predict and verify third-variant assignment order from lowest-count selection with first-in-array tie breaks

Current correct syntax

Per the live gh-aw templating reference (https://github.github.com/gh-aw/reference/templating/), conditional blocks are closed with {{/if}}, not {{#endif}} — confirmed example: {{#if expression}} ... {{/if}}.

Per the live A/B experiments reference (https://github.github.com/gh-aw/experimental/experiments/, "Statistical balancing" section):

If multiple variants are tied, including on the first run, one of them is chosen at random.

Tie-breaking is random, not deterministic first-in-array order, so the exact third/fourth/fifth-run assignment cannot be reliably predicted when counts are tied.

Suggested fix

  1. Replace both occurrences of {{#endif}} with {{/if}}.
  2. Update the explanation to: "gh-aw picks the variant with the lowest invocation count so far (ties, including on the first run, are broken at random)".
  3. Reword the related checkpoint item to reflect that tie-break order is random, so exact assignment order can only be predicted when counts are not tied.

Generated by 🔍 Workshop Sync Check · copilot · auto · 184.9 AIC · ⌖ 4.6 AIC · ⊞ 9.2K · ◷

  • expires on Oct 14, 2026, 5:02 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.