[workshop-sync] workshop/side-quest-13-01-pr-labeler-pattern.md: agent job uses write permission
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, github-actions
- Domain
- documentation
Research direction
Edit workshop/side-quest-13-01-pr-labeler-pattern.md: change the agent job's pull-requests permission from write to read and keep safe-outputs: add-labels. Read the permissions guidance in github-agentic-workflows.md and compare workshop/side-quest-13-03-pr-checklist-pattern.md. Run gh aw compile; done when the workshop file compiles with read-only agent permissions.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-13-01-pr-labeler-pattern.md (gh-aw v1.0.1)
Problem
The example frontmatter grants write access to the agent job:
permissions:
pull-requests: write
Current correct syntax
The gh-aw reference guidance (github-agentic-workflows.md) says to keep agent-job permissions read-only when writes are handled by safe outputs. Safe-output writes run in separate jobs with their own permissions. Strict mode, which is the default, also refuses write permissions. The compile step in the workshop is therefore likely to fail or teach an anti-pattern. Compare side-quest-13-03-pr-checklist-pattern.md, which uses pull-requests: read.
Suggested fix
Change pull-requests: write to pull-requests: read. Keep safe-outputs: add-labels. Re-validate with gh aw compile.
Note: workshop/side-quest-13-02-pr-summary-pattern.md has the same problem. It is tracked in a separate issue.
Generated by 🔍 Workshop Sync Check · copilot · auto · ~21 AIC · ⌖ ~1 AIC · ⊞ 4.7K · ◷
- expires on Oct 31, 2026, 8:04 AM UTC
- Dominant language
- JavaScript
- Stars
- 56
- Forks
- 40
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 13
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 72/100
githubnext/gh-aw-workshop#5297 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#5295 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#5293 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
githubnext/gh-aw-workshop#5283 ·
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 confirmed ordering issue, 3 cycles are false positivesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
githubnext/gh-aw-workshop#5282 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
0. Needs triage 35-feedback bug
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
oxc-project/oxc#28783 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
osmlab/name-suggestion-index#13056 ·
Maintainers usually reply within 2 days
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 68/100
githubnext/gh-cao#20168 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Sagargupta16/awesome-mcp-servers#297 ·
Maintainers usually reply within 1 day