[guidelines] workshop-builder.md: stale "section 2c" reference and --validate overuse
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Open .github/workflows/workshop-builder.md and inspect the stale section reference and both --validate instructions. Compare the compile guidance with .github/workflows/guidelines.md, then update the wording or commands as appropriate. Done means the reference names the current heading and the compile instructions follow the documented defaults and exceptions.
Written by the indexing model from the issue text.
Description
File reviewed
.github/workflows/workshop-builder.md
Violations
Stale internal section reference
Offending text:
Record:
- Whether the open PRs and issues satisfy the label-based blockers in the
eligibility table in section 2c
Suggested fix:
The file has no section literally labeled "2c" — headings in this file are not numbered (per the "Header style" rule). This appears to reference the "### Derive dispatch eligibility" subsection (under "## Assess Workshop Health"). Replace "section 2c" with a direct reference to that heading name, e.g. "the eligibility table under Derive dispatch eligibility", so the instruction stays accurate if headings are reordered.
Compile defaults — --validate used as default in Tier B
Offending text:
- Use the
agentic-workflowscompile tool with--validateon each file to
surface any schema errors or deprecated fields
and
- Re-run
agentic-workflowscompile with--validateon the modified file to
confirm the change is valid; fix any errors before proceeding
Suggested fix:
Per the "Compile defaults" rule in .github/workflows/guidelines.md, --validate should be reserved for targeted troubleshooting or schema/deprecation audits, not used as the default compile invocation. Consider whether these specific audit-style uses (schema/deprecation scan, post-edit validation) qualify as the allowed exception, or switch to the plain compile call and only add --validate when an error needs isolating.
Generated by 📋 Guidelines Enforcer · copilot · auto · 125.9 AIC · ⌖ 5.44 AIC · ⊞ 9.6K · ◷
- expires on Oct 10, 2026, 4:12 AM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 17
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
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#4417 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#4416 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 78/100
githubnext/gh-aw-workshop#4413 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4410 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4411 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
capricorn86/happy-dom#2485 ·
Maintainers usually reply within 2 days
-
area:space-accuracy good first issue track:data
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Sara-Managed-Projects/space-radar#904 ·
Maintainers usually reply within 1 day