Skip to content

Clarify what enables r? in triagebot #835

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2025
Merged

Clarify what enables r? in triagebot #835

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/triagebot/pr-assignment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,8 @@ When looking up a name, triagebot will first look at ad-hoc groups, then rust-la

PRs can only be assigned to users with write permissions to the repo, any rust-lang org members with read permissions, or anyone who has commented on the PR.

To enable the ability for users to post a comment with `r? name` to set the assignment to a specific user, add a `[assign]` table to `triagebot.toml`.

### Ghost

Using `r? ghost` in the initial PR top-level comment when opening a PR will disable triagebot's auto-assignment.
Expand Down Expand Up @@ -72,7 +74,6 @@ fallback = ["@Mark-Simulacrum"]
```

If the `owners` map is configured, then triagebot will automatically select a reviewer based on which files were modified in the PR.
The existence of the owners table also enables the ability for users to post a comment with `r? name` to set the assignment to a specific user.

### Vacation

Expand Down