[workshop-sync] 23-ab-experiments.md: incorrect templating closing tag `{{#endif}}`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 94/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, javascript
- Domain
- documentation
Research direction
Open workshop/23-ab-experiments.md and inspect the two conditional examples around lines 60 and 110. Replace each {{#endif}} with {{/if}}, then run gh aw compile to check that the conditional blocks close correctly.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/23-ab-experiments.md
Problem
The file uses {{#endif}} as the closing tag for conditional template blocks in two code examples (lines 60 and 110):
{{#if experiments.output_style }} ... {{#endif}}
Current correct syntax
gh-aw's templating syntax closes {{#if ...}} blocks with {{/if}}, not {{#endif}}. This is confirmed by:
/tmp/gh-aw/data/ref/syntax-agentic.md(line 83):{{#if experiments.<name> }}is the opening form, implying the standard{{#if}}...{{/if}}pairing.- Live usage in this repo's own compiled workflow source
.github/workflows/q.md(lines 52-86), which consistently uses{{#if ... }}paired with{{/if}}.
Using {{#endif}} instead of {{/if}} will cause the conditional block to fail to close correctly when compiled with gh aw compile.
Suggested fix
Replace both occurrences of {{#endif}} with {{/if}} in workshop/23-ab-experiments.md (lines 60 and 110).
Generated by 🔍 Workshop Sync Check · copilot · auto · 131.7 AIC · ⌖ 5.63 AIC · ⊞ 9.2K · ◷
- expires on Oct 7, 2026, 5:02 AM UTC
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 23
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 22
Getting set up
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4251 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4249 ·
Maintainers usually reply within 1 day
-
agentic-workflows documentation workflow-editor
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
githubnext/gh-aw-workshop#4246 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4242 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#4243 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 2/5 Under an hour Newbie friendliness 85/100
capricorn86/happy-dom#2474 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
juice-shop/juice-shop#3662 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Add unit-test coverage for API URL resolution and device authentication error handlingPossibly taken @Simranjit8933 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
fossasia/eventyay-checkin#170 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day