feat(web): sort pull requests by what is blocked on me

[flamboh]

Note

🤖 Claude Fable 5.1 on behalf of Oliver

ELI5

A new sort on the Pull Requests tab, "Blocked on me", puts the PRs that are waiting on you at the top.

Why

The default "Merge readiness" sort is the maintainer's view: green and approved work first. There was no contributor's view. Your own PR with a conflict, a red build, or a changes-requested review sat wherever its checks put it, and a PR waiting on your review was only findable by scanning the Review requested section.

Implementation

Adds a blocked sort next to the existing ones. Like every other sort, it orders rows inside the existing Authored, Review requested, and Others sections and never moves a row across them. The Others section is left untouched when involvement is All, since nothing there is blocked on the reader.

Order criteria for the Authored section (and the whole list when involvement is Authored):

• Conflicting with base
• Changes requested
• Checks failing
• Draft
• Open and waiting on others: review required, checks pending, or no verdict reported by the host
• Approved with passing checks
• Closed or merged

Order criteria for the Review requested section (and the whole list when involvement is Reviewing):

• Open requests
• Closed or merged

Within every tier, the most recently updated row comes first. A search keeps its relevance order, as it does for Merge readiness. Hosts that report no review decision or check rollup land in the waiting tier, never in a fixing one.

The sort is persisted with the other list preferences and appears in the URL as sort=blocked. It does not rank by diff size, so it does not trigger the eager line-count fetch.

UI Changes

Before

Merge readiness on a sandbox repo seeded with one PR per tier.

After

Blocked on me on the same list.

The new entry in the Sort menu.

---

Claude Fable 5.1 via Claude Code in T3 Code, with Luna (Codex) for implementation.

Summary by CodeRabbit

• New Features

  • Added a “Blocked on me” sorting option for pull request lists.
  • Pull requests can now be prioritized based on whether they are blocked on the current user as author or reviewer.
  • Sorting respects the selected involvement scope and applies to grouped pull request views.

• Tests

  • Added coverage for blocked-on-author, blocked-on-reviewer, and grouped sorting behavior.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds an opt-in, tested “Blocked on me” sorting capability that changes pull-request ordering based on authored and review-requested status. The default behavior remains unchanged, but the feature modifies shared production list logic and route behavior, warranting human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: b97a8c98-b7c7-462d-bdb4-9bcd9e1227b0

📥 Commits

Reviewing files that changed from the base of the PR and between 82cd1d1 and d3876cb.

📒 Files selected for processing (4)

• apps/web/src/components/pullRequest/pullRequestList.logic.test.ts
• apps/web/src/components/pullRequest/pullRequestList.logic.ts
• apps/web/src/components/pullRequest/pullRequestListPreferences.ts
• apps/web/src/routes/_chat.pull-requests.tsx

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request list adds a “Blocked on me” sort. It ranks authored and review-requested pull requests by blocked status and recency, uses involvement for other groups, and preserves existing group order during searches.

Changes

Blocked pull request sorting

Layer / File(s)	Summary
Blocked ranking rules and validation apps/web/src/components/pullRequest/pullRequestList.logic.ts, apps/web/src/components/pullRequest/pullRequestList.logic.test.ts	Adds author-blocked and reviewer-blocked ranking functions with status tiers and recency ordering. Tests cover ranking and group behavior.
Involvement-aware group sorting apps/web/src/components/pullRequest/pullRequestList.logic.ts	Adds the involvement parameter and applies role-specific ranking in blocked mode. Searches leave groups unranked.
Blocked sort menu wiring apps/web/src/components/pullRequest/pullRequestListPreferences.ts, apps/web/src/routes/_chat.pull-requests.tsx	Adds the blocked sort value, its “Blocked on me” menu entry, and involvement input wiring.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Feature

Suggested reviewers: maria-rcks

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant SORT_OPTIONS
  participant sortPullRequestGroups
  participant rankPullRequestsBlockedOnAuthor
  participant rankPullRequestsBlockedOnReviewer
  User->>SORT_OPTIONS: select "Blocked on me"
  SORT_OPTIONS->>sortPullRequestGroups: pass blocked sort and involvement
  sortPullRequestGroups->>rankPullRequestsBlockedOnAuthor: rank authored groups
  sortPullRequestGroups->>rankPullRequestsBlockedOnReviewer: rank review-requested groups
  rankPullRequestsBlockedOnAuthor-->>sortPullRequestGroups: return author-blocked order
  rankPullRequestsBlockedOnReviewer-->>sortPullRequestGroups: return reviewer-blocked order

Loading

Merge Risk: ⚪ Minimal · up to d3876

The blocked sort is wired through preferences and URL state, preserves search relevance, and applies the intended ordering for each involvement view. No actionable merge risk was identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 6 functions across 4 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a web sort for pull requests blocked on the current user.
Description check	✅ Passed	The description explains what changed, why it changed, implementation details, and UI changes with before-and-after screenshots. It does not include the repository checklist, but the main required inf…

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}