Workflows

Triage pull requests you author

Use Involving me across repositories, or choose one repository to change the queue to My PRs. Your pull requests receive plain-language Notes derived from loaded CI, review, comment, conflict, draft, label, and linked-issue data. Treat the Note as the next signal to inspect, not as an automated action.

While a pull request waits for a reviewer, its Note ends with how long it has waited, such as · 16h or · 3d, in amber once the wait is stale. Drafts and pull requests someone has already reviewed show no wait. Awaiting review lists the longest wait first. When only a team was asked and nobody has reviewed yet, the Note says “team requested, nobody responded”; when nobody was asked at all, it says “no reviewers”.

1. Scan actionable rows first and open Details for the loaded metadata.
2. Open the PR in GitHub when you need the full conversation or want to act.
3. Use Changed to narrow the loaded rows to updates since PR Marmot last saw them. Hover the blue marker to see what changed: new commits, CI, reviews, requests, or unresolved comments. It clears only when you actually select that PR.
4. Search the loaded rows, or filter them by label, author, or repository.

To share a section, such as Awaiting review, hover its header and choose Copy, or right-click the header. Copy list for Slack & docs pastes titled links into Slack, Teams, Google Docs, Notion, Linear, and Jira. Copy Markdown for GitHub, Copy as table, and Copy URLs cover the rest. Press Y to copy the selected PR's section as a list. Copies respect the active search, and on Linux the list and table copy as plain text.

Reviewer suggestions in authored Notes are static hints from default_reviewers, or from [repo_reviewers] for a repository or its owner. PR Marmot does not assign those people, validate repository ownership, or interpret CODEOWNERS.

Requested and available reviews

The Review queue has two different kinds of work. Requested means your GitHub user was explicitly requested. Available to review means an other-authored PR has no pending user or team review request in the loaded data. Available work is an optional pool, not an assignment.

In the Review queue, a Note also ends with the size of the change: Small (at most 100 changed lines and at most 10 files), Large (more than 400 lines or more than 30 files), or Medium. Changed lines are additions plus deletions as GitHub counts them, so lockfiles and generated files count too, and a pull request whose counts GitHub didn’t report shows no size. The size is never turned into a time estimate. Its thresholds follow Google’s small-change guidance.

Requested from you and Available to review list the longest wait first. Turn on Smallest first in the toolbar to list them by size, then by changed lines, then by wait; it lasts until you quit.

Use labels and repository context to choose useful work, then open the PR on GitHub. Your own PRs are excluded from this queue. Availability is based on review requests, not issue assignees, and PR Marmot never assigns, reviews, comments on, or merges a pull request.

Native GitHub stacks are grouped by stack metadata and ordered from the base upward. Grouping is not guessed from branch names or labels. If all layers are not present in the same loaded section, PR Marmot reports a partial stack rather than implying the group is complete.

Search and filter

Click Search, press /, or press ⌘F (Ctrl+F on Linux). Words match the PR number, repository, title, author, label, issue, and Note. Several words narrow together, and quotes keep a phrase whole. The count beside the box shows how many loaded pull requests match.

• label:NAME, author:LOGIN, and repo:OWNER/NAME keep pull requests whose label, author, or repository is exactly that, ignoring case. Quote values with spaces: label:"help wanted".
• is:stale keeps pull requests that have waited for a reviewer for stale_after_days (three by default) or longer.
• A finished term becomes a chip, and every chip and word must match. Click a label, author, or repository in the table to add one; labels work from Details too. A chip’s × removes it, and Backspace in an empty box removes the last one.

Search works on the loaded rows and makes no extra GitHub request.

Watch, snooze, and return

Watch a selected PR with w when its next meaningful transition matters. Watches are FIFO-bounded at 50 and refresh in one batched GraphQL operation, including watched PRs outside the active search. Notifications are suppressed for the first successful observation after launch and for the focused selected row.

Snooze with s for one hour, until tomorrow, while waiting on a person, until terminal CI finishes, or until a reviewed PR changes. Snoozed rows move to a collapsed group and stop contributing attention alerts and counts until they wake.

Search, Changed, Details, and stack grouping all operate on the loaded snapshot; they do not issue one request per PR. Initial involvement or authored searches load up to 60 PRs. Review mode loads up to 60 requested PRs and 60 candidates before filtering and deduplication. A partial-results notice means more data exists. Load more advances each active search for at most five pages—up to 300 authored results or 600 review candidates before filtering. Refresh returns to page one, and a failed extra page leaves existing rows in place.

See Reference for refresh behavior and all shortcuts.