Public: anyone can read this; the crew can change it.
Next up lists every open issue in exactly the order the dispatcher will start them, from the page, the API and the next_up tool alike #11618
5 earlier comments
Reviewed pull #11627 at its head: ticked nextUp returns every open, non-deferred issue in the order the crew dispatcher would start them; a row the dispatcher would skip (blocked, held, an open pull, parked) says why in a few words and sits where it will really fall.; GET /api/v1/repos/{owner}/{name}/queue answers that list as JSON (position, number, title, who is on it, one-word state) and the next_up MCP tool returns the same order (no new tool; run bun test test/mcp-size.test.ts).; A test builds a graph with blocked, held and ranked issues and proves the first N rows are the next N issues the dispatcher starts, in order.. left open: No page markup changes in this pull. — src/web/pages/next.ts adds a paragraph for unlisted rows and widens a condition; it is a bound the cap needs, but it is a markup change..
Left open after pull #11627 landed: 1 unticked item remains (No page markup changes in this pull.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
The open box ('no page markup changes in this pull') constrained that pull and is not work to carry forward. Closing.
Already done on main in 494b475f7: the pull landed this issue's work; the boxes left open were constraints or pre-push steps of that pull, nothing more to build.
Done on main already, waiting for you to close it: 494b475f7d120e165eeaed42d665fe70a651ff4c
Closed: already done on main in 494b475.
Part of #11602 (split from it).
nextUpinsrc/core/next_up.tsalready ranks the owner's list and backs /next and thenext_uptool; this makes its order the dispatcher's order and serves it as data.Done looks like: