[workshop-sync] side-quest-13-01-pr-labeler-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
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- devops, documentation
Research direction
Open workshop/side-quest-13-01-pr-labeler-pattern.md and compare its frontmatter with workshop/14b-pr-reviewer-workflow.md and the repository workflows. Check the gh-aw safe-outputs guidance for the add-labels cap and job permissions. Done when the example uses the supported cap key and read-only pull request permission.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-13-01-pr-labeler-pattern.md (against gh-aw v0.93.0)
Problem
The example frontmatter caps the safe output with limit::
safe-outputs:
add-labels:
limit: 5
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 to keep the agent job read-only, since safe-output writes run in separate jobs with their own permissions.
Suggested fix
- Replace
limit: 5withmax: 5. - Change
pull-requests: writetopull-requests: read.
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 8h
- 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
-
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 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4878 ·
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
All issues in githubnext/gh-aw-workshop
Similar issues
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Update to mocha 12.xOpen
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rescript-lang/rescript#8996 ·
Maintainers usually reply within 1 day
-
check:passed logos:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100