[workshop-sync] side-quest-13-02-pr-summary-pattern.md: safe-outputs uses invalid 'limit' key (should be 'max')
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- devtools, documentation
Research direction
Read workshop/side-quest-13-02-pr-summary-pattern.md and compare its safe-outputs configuration with workshop/14b-pr-reviewer-workflow.md and the safe-outputs reference linked in the issue. Update the cap key and permission, then check the empty journey block and add the return link to match sibling side quests. Done when the example follows the documented configuration and workshop conventions.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-13-02-pr-summary-pattern.md (against gh-aw v0.93.0)
Problem
The example frontmatter caps the safe output with limit::
safe-outputs:
add-comment:
limit: 1
The safe-outputs cap key is max: (as used in workshop/14b-pr-reviewer-workflow.md and this repo's own workflows). limit is not a documented safe-output field, so compilation may fail or the cap is ignored.
The example also grants pull-requests: write. gh-aw guidance is that add-comment needs only pull-requests: read for the agent job; the write happens in a separate safe-output job.
Suggested fix
- Replace
limit: 1withmax: 1. - Change
pull-requests: writetopull-requests: read. - Minor: the file ends with an empty
journeyblock and no return link, unlike its sibling side quests.
Reference: https://github.github.com/gh-aw/reference/safe-outputs/
Generated by 🔍 Workshop Sync Check · copilot · auto · 30.9 AIC · ⌖ 0.568 AIC · ⊞ 9.2K · ◷
- expires on Oct 23, 2026, 8:40 PM UTC
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 36
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 14
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
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4897 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4896 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4885 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
githubnext/gh-aw-workshop#4879 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4877 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
thedevs-network/kutt#1059 ·
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day