Next up

/:owner/:name/next is the one ranked list the crew builds from (#8694). It reads as one numbered queue in the dispatcher's order (#11619): each row has its position, title, who is on it (or "next"), and one word of state: building, checking, in review, landing, waiting on #N, held or ready. A pull that is open on the issue sets building, checking or in review. Three native folds hold the rows, each with a count: "Up next" (the first ten, open), "After" (the rest) and "Later" (behind the Later gate). There is no script for the folds and no ?all=1; the folds are keyboard and screen-reader reachable at any width. The terminal's Next up screen shows the same numbers and state words.

Terminal: the palette's "Next up in a repository" opens the same list; t, u, d and l are Top, Up, Down and Not now on the row under the cursor, through the same action as the page and MCP. A reader sees the order and the keys do nothing; a move made anywhere reorders an open screen live. At most 200 issues are ranked; a move past that is refused and says so.

Filter (#11867): a plain GET form above the list narrows /next to one pillar (?pillar=P7 or Later, typed in a box) and/or a word (?q=cache, matched without regard to case, shown as typed, at most 80 characters). A filter only hides rows: each keeps its real place in the whole ranking, the cut line stays where the whole list puts it (drawn only between shown rows), and a move made under a filter moves in the whole order and returns to the same filter. A line says "N of M shown", and that the week's capacity bar is left out while filtered. An unknown or malformed pillar shows an empty list that says so. Terminal: / asks for a pillar and/or a word (P7 cache); an empty answer clears it; ranks, t u d l and the header count behave as on the page.

The chapter line (#12681): under the title, once the repository has chapters, Ranked for <open chapter>: <progress sentence> (linked), or "No chapter is open" with a link to draft one; a repository that never drafted a chapter shows no line. Terminal: the screen prints the same line under the title, from the same function (chapterLineParts in core/chapters.ts), wrapped to the width and never cut (#13254, #12991).

The growth line (#12290): under the title, two dl rows: Week (issues opened in the last seven days, who opened them, how many closed, and what is open now: "2 issues opened (2 by owner), 0 closed. 2 open (2 issues, 0 pulls).", #12867: one row, so the numbers are said once) and Planner (on, paused until a time in UTC, or paused until the owner switches it on). The owner (a person who administers the repository) also gets the switch in the Planner row: a button in a post form to the same planner_switch action as the queue page, sent back to /next, so the pause is one tap and the owner stays on the list. A reader sees both rows and no button. Both rows come from one read (weekLine, which also counts open issues and pulls and what opened and closed today), sealed issues left out for a viewer who may not see them. Terminal: Next up shows the same sentence (growthWords, pauseSentence) above the list, and the owner presses p to pause the planner until they switch it on, and p again to switch it on; for a reader and for an agent the key does nothing.

The week is the sprint (#8704)

The subscription's weekly reset is the sprint boundary; what the crew may still spend before it is the capacity (flow/week.ts, from core/standing.ts). No ceremony and no locked scope: rerank any time and the line moves on the next paint.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs