Asks & routing

A directed ask (👤) is Queuebird surfacing the specific people a PR is waiting on. Asks come from two places, unified into one list: GitHub’s review requests (picked up automatically) and /qb add @mention. Each newly-asked person who’s linked gets a gentle once-per-PR DM: “👤 You’ve been asked to review …”. On your personal NEEDS YOU list, being asked boosts a PR’s sort order.

The re-review marker (🔄) lights in two cases: new commits landed after a reviewer’s last review, or GitHub re-requested a review from someone who already reviewed. Either way, the PR re-enters that reviewer’s NEEDS YOU list for another look, marked 🔄. The once-per-PR ask DM doesn’t repeat on a re-request — only the first ask sends one.

Team asks

Mentioning a team — a Slack usergroup tag, or a GitHub team review request — is a different kind of ask: it puts the PR in that team’s own queue, running on that team’s own SLA clock, escalation, and stats, not just a name on a card. Mention more than one team (or GitHub itself requests more than one) and the PR lands in every one of their queues at once — Queuebird never makes you pick. The disambiguation prompt (“which team should review this?”) is reserved for when nothing resolves on its own: no team asked, no repo owned by exactly one queue, and more than one queue to choose from — see Queues & intake for the full routing order.

One exception: a bare paste inside a queue channel never creates extra homes from @team mentions in the message text — that channel is already private team space, so a tag there is decoration, not a cross-team ask. To ask another team from inside a queue channel, use /qb add <pr-url> @team instead.