Grant required permissions on reusable workflow callers#21
Merged
Conversation
The shared `claude-responder` and `claude-review` reusable workflows declare job-level permissions (contents: write, etc.) but reusable workflows can only inherit caller permissions, never elevate. Without explicit `permissions:` on the calling jobs, GitHub Actions rejects the workflow with "is requesting X but is only allowed Y" startup errors and refuses to start any job. Add the required permissions blocks to the responder and review caller jobs to match what the reusable workflows declare. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
permissions:blocks to theclaudeandclaude-reviewjobs that call the shared reusable workflows. Reusable workflows can only inherit caller permissions, never elevate them — without these blocks, every responder/review run fails withstartup_failureand the message "is requesting X but is only allowed Y".Why
PitziLabs/shared-workflowsdeclare the permissions they need (contents: write, pull-requests: write, etc.). When the caller doesn't grant at least those, GitHub rejects the workflow at parse time.Test plan
@claudemention and amodel:haikulabel; confirm the responder workflow runs (no startup_failure) and routes to Haiku.🤖 Generated with Claude Code