Read the open pull requests list

Open pull requests is the page Limn opens on. It lists every open pull request in the workspace, drafts included, one row each, across every repository. Each row shows whether the pull request can land, its checks, its review, its open threads and its AI review. Select a row to see the rest in a side panel. The default branch strip sits at the top.

#What you see

The page has two tabs, Open and Merged. Open is the list described here. Each row has two lines:

• The first line: a coloured mark, the title, then four columns: Review (approved in green, changes requested in red), CI (a red cross, a tick, or a ring while checks run), Threads (open review threads; a red dot means one has no reply) and AI review (see the AI review column).
• The second line: the repository and number, the author and the age.

The mark at the start of the row is red when the pull request has merge conflicts or is blocked, green when it can land, and grey otherwise. It uses the same rules as the pull request's own Can it land row.

The side panel

Select a row to open its side panel. The panel holds everything the row leaves out, in words: Can it land, Checks, Reviews, Threads, the author, when it was opened and updated, its Size and Reach (the blast radius), and the full AI review. The panel's place is kept even when it is empty, so the list does not move when you open or close it.

While GitHub’s merge queue holds the pull request, a Merge queue row under Can it land says where it is, for example “In the merge queue · running checks”, or “Leaving the merge queue” when GitHub is taking it out.

#Grouped by ticket

Where the workspace has an issue tracker connected, the list is grouped by ticket. Each group shows the ticket's key and name; choose it to open the ticket's story view. A pull request that names two tickets is in both groups. Pull requests with no ticket are in a last group, No ticket. Tickets that are not done come first, then the most recently updated.

Choose Group by ticket or List to switch. Limn remembers your choice in this browser. On a slow tracker, Limn shows the plain list after a few seconds and offers to regroup when the tickets arrive.

#What you can do

Open a pull request

1. Select a row (click it, or press j and k) to open its side panel.
2. Double-click the row, or press ↵ again, to open the pull request in its own tab. See Open a pull request.

o opens the selected pull request on GitHub, and r opens its AI review.

Use the row menu

Right-click a row (or press ⇧ F10 on the selected row) for its menu: Merge, Overview, Changes, Threads and AI Review. Each one opens the pull request on that tab. Merge shows only when the pull request can land now, is not a draft, is not in GitHub's merge queue, has no merge armed, and you can push to the repository. Choosing it opens the merge options; nothing merges until you confirm there.

Where the AI features are on, the menu also has Start review. It starts an AI review with the same choice the AI Review tab opens on: Claude + Codex when both are signed in, else your default provider. It keeps the review in Limn and posts nothing. It is greyed out, with the reason beside it, while AI is not set up or signed in, while a review of that pull request is starting, queued or running, and when the last review is on the latest commit. See The AI review column.

Copy GitHub URL, at the bottom of the menu, copies the pull request’s github.com address.

Sort and narrow the list

• Sort: Recent activity (the default), Updated, Opened, Size, Untouched threads, CI, Approval, Repo, Author and PR number, plus AI review and AI findings where the AI features are on. The arrow beside the menu reverses the order. The menu always names the order on screen, for example "Opened, oldest first". With groups, the sort orders the rows inside each group.
• The repository menu narrows the list to one repository. It affects this page only.

#The Merged tab

Merged lists every pull request that merged in the workspace's reporting window (for example, the current sprint), newest merge first, with the same ticket groups. Where the tracker and the AI features are on, each ticket keeps its story check. See The reporting window.

#Why it helps

GitHub lists pull requests one repository at a time. This page shows all of them for the workspace, with the facts that decide what to do next, on one line each. Grouping by ticket shows which pieces of one story are still open. Use Pending when you want the same work sorted by what to do first.