Work from the Pending board

Pending is everything waiting on you or your workspace, across every repository, in eight tabs. Each item is one line; select it to see the whole card in a side panel, with the buttons to act on it. Pending is worked out again every time it loads, from what GitHub says now. An item leaves when the work it describes is done.

#The tabs

The number on a tab is everything in it. A tab lists up to 50 of each kind of item and says when it holds more. Where a tab holds two kinds, chips above the list narrow it to one.

#How each tab is ordered

My turn is not scored. It has fixed groups, with the longest wait first in each. See My turn. Dependencies puts every security item before every bump. AI reviews is newest first, and Waiting on others is longest wait first.

Every other tab lists its items by a score out of 100, highest first. The score has three parts:

• How close to done (50%). The next step: an approved pull request that is ready to merge is closest; then one that needs a branch update, a failing default branch, a failing build, a review, a reply, an unanswered thread, and last, waiting on a reviewer. A merge conflict or many unanswered threads lower it a little; a small change raises it a little.
• How long it has waited (30%). Measured from the moment that matters for the item: when you were asked, the last commit, or when the thread started.
• How much it is about you (20%). Most when it names you, less in a repository you maintain, least for shared work.

The top five in a scored tab are Do next; the rest are under Everything else. Items in one tab usually share their next step, so the order mostly comes down to how long each has waited and how small the change is. The weights are fixed.

Colours

The mark at the start of a row is red when the item blocks a merge or a build (a failing build, a merge conflict, a security alert), green when it can land now, amber when it is urgent and neither of those applies, and grey otherwise. Colour does not change the order.

#What you can do

1. Choose a tab, or press 1 to 8.
2. Select an item (a click, j or k) to open its card in the side panel. Nothing is selected when the page opens.
3. Act from the card's buttons, or with a key: a approve, m merge, e dismiss (My turn), o open on GitHub.
4. Go to the item itself with a double-click, ⇧ ↵, or the arrow in the panel's header. A review request opens the pull request's Changes tab, a thread opens that thread, an AI review opens the AI Review tab, and a failing build or a merge opens the Overview.

Dismiss, approve and merge offer Undo for a few seconds (z). Approve and merge are sent only when the offer ends.

Narrow a tab

• Kind chips, on a tab that holds two kinds (for example, failing builds and conflicts).
• Anyone · People · Automation: by who opened the pull request. Shown only when both sides have items.
• Only yours · Not tied to you, on My turn. See Only yours.

#The first day

For the first two weeks after you add your first repositories, Pending shows a one-line summary of what it found. If every tab is empty, it lists your own open pull requests, newest first, with what blocks each one.

#Why it helps

Pending answers "what should I do next?" for a whole workspace. Each item says why it is there and why it sits where it does, so you can trust the order or disagree with it. The tabs keep different kinds of work apart, so a merge never competes with a review for the top place.