Skip to content

Commit 9791019

Browse files
committed
Fix nits
1 parent 36164b1 commit 9791019

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/triagebot/review-queue-tracking.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# Review queue tracking
22

3-
Triagebot supports more advanced tracking of reviewers' workload in the `rust-lang` repository. It tracks how many "relevant" pull requests are assigned to each reviewer, and allows reviewers to configure maximum capacity of such PRs, and also if they want to be automatically assigned or not.
3+
Triagebot supports more advanced tracking of reviewers' workload in the `rust-lang/rust` repository. It tracks how many "relevant" pull requests are assigned to each reviewer, and allows reviewers to configure maximum capacity of such PRs, and also if they want to be automatically assigned or not.
44

5-
This pages describes how the review queue works and how you can interact with `triagebot` on Zulip to configure and examine the review queue.
5+
This page describes how the review queue works and how you can interact with `triagebot` on Zulip to configure and examine the review queue.
66

77
## Configuration
88

99
To enable review queue tracking for a repository, include `[pr-tracking]` table in its `triagebot.toml`.
1010

1111
To take the review queue into account when assigning reviewers on PRs, add a `[assign.review_prefs]` table to `triagebot.toml`.
1212

13-
> Note that this functionality currently only works only for the `rust-lang/rust` repository (it is hardcoded in `triagebot`). Enabling it for more repositories requires additional design and implementation work.
13+
> Note that this functionality currently only works for the `rust-lang/rust` repository (it is hardcoded in `triagebot`). Enabling it for more repositories requires additional design and implementation work.
1414
1515
## Review queue design
1616

@@ -24,7 +24,7 @@ Currently, the heuristic for what makes a PR "relevant" works as follows:
2424

2525
If a PR passes all these checks and it is assigned to reviewer `R`, it will be considered to be in `R`'s review queue.
2626

27-
See the implementation of the [`waits_for_a_review`](https://github.com/rust-lang/triagebot/blob/HEAD/src/handlers/pr_tracking.rs#L289) function in triagebot for more details.
27+
See the implementation of the [`waits_for_a_review`](https://github.com/rust-lang/triagebot/blob/7044e5449aaf29eea939bc7db81c63b7c872b9b8/src/handlers/pr_tracking.rs#L277-L304) function in triagebot for more details.
2828

2929
## Review preferences
3030

0 commit comments

Comments
 (0)