Repository navigation
fix: correct Claude bot permissions - #78
Merged
Merged
Conversation
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
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
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
contents: writeto the Claude mention-bot caller jobid-token: write, which is part of the upstream Claude Code Action permission setRationale
The reusable
claude-code-bot.ymlrequestscontents: write, but a reusable workflow cannot elevateGITHUB_TOKENpermissions above those granted by its caller. The caller currently grants onlycontents: read, preventing Claude from applying repository content changes when invoked by an authorized mention.The reusable workflow already restricts execution to
OWNER,MEMBER, orCOLLABORATORauthors.