rodin/review-bot
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

docs: add read:user to required token scopes #67

Merged
aweiker merged 1 commits from issue-66 into main 2026-05-11 06:52:22 +00:00
Conversation 4 Commits 1 Files Changed 1
+3 -2
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -329,11 +329,12 @@ All flags have environment variable equivalents:
### Token Scopes Required
gpt-review-bot commented 2026-05-11 06:42:25 +00:00
Review
Copy Link
Copy Source

[NIT] Section title says 'Token Scopes Required' but the table includes an optional scope (read:user). Consider renaming to 'Token Scopes' or splitting into 'Required' and 'Optional' for clarity.

**[NIT]** Section title says 'Token Scopes Required' but the table includes an optional scope (`read:user`). Consider renaming to 'Token Scopes' or splitting into 'Required' and 'Optional' for clarity.
| Scope | Purpose |
|-------|---------|
|-------|--------|
sonnet-review-bot commented 2026-05-11 06:41:55 +00:00
Review
Copy Link
Copy Source

[NIT] The header separator row changed from |-------|---------| to |-------|--------| (one fewer dash in the second column). Both are valid Markdown table syntax, but the inconsistency with the surrounding table style is trivially cosmetic.

**[NIT]** The header separator row changed from `|-------|---------|` to `|-------|--------|` (one fewer dash in the second column). Both are valid Markdown table syntax, but the inconsistency with the surrounding table style is trivially cosmetic.
| `write:issue` | Post and delete reviews |
| `write:repository` | Read PR diffs, file content, commit statuses |
| `read:user` | Self-request as reviewer (optional but recommended) |
No `read:user` scope needed — the bot identifies itself from the review response.
Without `read:user`, the bot still works but cannot add itself to the PR's reviewer list.
## Development