Share code review duty without a rota

Why rotate it

Pull requests wait longest when everybody assumes somebody else will review them. Naming a reviewer of the day, or of the week, removes the guesswork: one person owns the queue, and everyone else can stay focused.

Doing that by hand tends to fall on the same senior engineer, who quietly becomes the team's permanent reviewer. Who'll Do takes the decision off anyone's plate.

Point a schedule at your engineering channel, or at a Slack user group such as @reviewers so only the right people are in the draw. Fair mode rotates through everyone before repeating. When the week's reviewer is swamped, "Can't, pick someone else" re-picks without ever landing back on them, and the History view in the app shows how the load has been shared over the last twelve weeks.

Prefer to pick on demand? Type /wholl-do pick @reviewers in any channel for an instant, fair pick.

Setting it up takes a couple of minutes. Add the app, choose the Code review of the day template from the welcome message, and point it at the channel where pull requests are announced. Switch the pool to a user group or a hand-picked list if only some people review.

Teams that do this well agree on what the reviewer owns: first response within a few hours, a clear approve or request-changes, and pulling in a second reviewer when the change touches unfamiliar code. Writing that down once makes the rotation feel fair as well as random.

Need a one-off order right now? Try the free standup randomizer: paste names, shuffle, done. No signup.