[workshop-sync] workshop/side-quest-13-02-pr-summary-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
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
Research direction
Open workshop/side-quest-13-02-pr-summary-pattern.md and compare its permissions with the guidance in github-agentic-workflows.md. Change the agent job's pull-requests permission to read, keep safe-outputs: add-comment, then run gh aw compile to validate the workflow.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-13-02-pr-summary-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: "add-comment needs pull-requests: read to inspect a PR, not pull-requests: write". Safe-output writes run in separate jobs with their own permissions. Strict mode, which is the default, refuses write permissions.
Suggested fix
Change pull-requests: write to pull-requests: read. Keep safe-outputs: add-comment. Re-validate with gh aw compile.
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 15h
- 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 74/100
githubnext/gh-aw-workshop#5224 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
githubnext/gh-aw-workshop#5222 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#5218 ·
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 early-reference issue, 2 missing next links, loops benignOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#5212 ·
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 confirmed ordering issue, 3 loops reviewed as intentionalOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#5211 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
【错误报告】界限突破·于吉「蛊惑」结算崩溃：reguhuo_final 中 chooseToDiscard().forResult() 可能返回 undefined（result.bool 未判空）Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/twake-drive#4494 ·
Maintainers usually reply within 1 day
-
[quality] /resources/metrics draws the single-point member-companies chart on the left axisPossibly taken @hivecommons-hive claimed this today. Openagent/quality stage/040-covered-by-pr testing
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day