The reviewer-token needs specific Gitea scopes to function properly:
Required scopes:
write:issue - to post reviews
write:repository - to read PR diffs
read:user - to check if PR author matches reviewer (skip self-reviews)
Without read:user, the bot logs:
level=WARN msg="could not determine authenticated user for reviewer self-request" error="...required=[read:user], token scope=write:issue,write:repository..."
The README should document these required scopes so users know to set them when creating tokens.
The `reviewer-token` needs specific Gitea scopes to function properly:
**Required scopes:**
- `write:issue` - to post reviews
- `write:repository` - to read PR diffs
- `read:user` - to check if PR author matches reviewer (skip self-reviews)
Without `read:user`, the bot logs:
```
level=WARN msg="could not determine authenticated user for reviewer self-request" error="...required=[read:user], token scope=write:issue,write:repository..."
```
The README should document these required scopes so users know to set them when creating tokens.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
reviewer-tokenneeds specific Gitea scopes to function properly:Required scopes:
write:issue- to post reviewswrite:repository- to read PR diffsread:user- to check if PR author matches reviewer (skip self-reviews)Without
read:user, the bot logs:The README should document these required scopes so users know to set them when creating tokens.