ci: add write permissions for issue monster agent assignment#537
ci: add write permissions for issue monster agent assignment#537
Conversation
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
|
🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨ |
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤 |
✅ Coverage Check PassedOverall Coverage
Coverage comparison generated by |
There was a problem hiding this comment.
Pull request overview
This PR fixes a permission issue preventing the assign_to_agent tool from functioning in the Issue Monster workflow. The tool was failing with "Resource not accessible by personal access token" because the replaceActorsForAssignable GraphQL mutation requires four specific write permissions.
Changes:
- Updated workflow permissions from read-only to write access for
actionsandcontents - All four required permissions (
actions,contents,issues,pull-requests) now have write access - Changes applied consistently to both the source
.mdfile and compiled.lock.ymlfile
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/issue-monster.md |
Updated top-level permissions to grant write access for actions, contents, issues, and pull-requests |
.github/workflows/issue-monster.lock.yml |
Applied permission updates to three jobs (agent, conclusion, safe_outputs) that require access to the assign_to_agent functionality |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Claude Smoke Test ResultsLast 2 merged PRs:
Test Results:
Status: PASS
|
The
assign_to_agentsafe-outputs tool fails with"Resource not accessible by personal access token"because thereplaceActorsForAssignableGraphQL mutation requires four write permissions, but the workflow only had read access foractionsandcontents.actions: writeand upgradedcontents: read→contents: writeon theagent,conclusion, andsafe_outputsjobs in the lock fileissue-monster.mdsource permissions to matchOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.