A repository standing still behind its pulls (#12611)
A repository stands still when it has at least three open pulls and every one is red (its latest check on its head failed) or untouched for three days. Its ready issues cannot start while those pulls hold them (open_pull). This is a place to explore, so some repositories will: it is said calmly, in one place, and never on the home page. A repository that is turned off (archived) is never counted.
It is said in one sentence on every door (pileSentence): "trevato/scratchpad: 38 pulls nobody has touched since 2 Nov. Nothing new can start there until they move."
- Needs stack.
flow/stuck_pile.tsfinds it;actions/needs.tsraises it once, by name, for whoever writes to the repository: the terminal's "How is my forge?" (rre-checks its pulls,hhands them to builders,ccloses them after asking for a reason,oturns the app off; each shows its plan, a dry run, and acts only on a yes) and the MCPforgetool. - Its page.
/asks, under "Standing still" (web/studio/standing.ts): a row per repository with the sentence and its choices as buttons, then a row per approved pull a week old that has not landed, linked to the pull. The home page (/) shows none of this: its lanes come first, and its one line counts only what is broken about the forge itself. - Choices (
crew/stuck_pile.ts, a person's word only, a writer's access): re-check its pulls on today's main (at most 50 a call, the check queue's own order), hand each to the builder that opened it, close them with a reason (their issues go back to ready, unassigned), or turn the app off. Web:POST /:owner/:name/stuckwithchoice(recheck,builders,close,off) andreason, then back to the page the form was on (next:/asksor the repository's pulls). MCP:forge {apply: "stuck:<repo id>", choice, reason?, dryRun?}, planned first unlessdryRun: false. - Turn this app off. Not a new mechanism: it is the repository's archive (
setArchived, the MCParchivetool, Settings). The app, its previews and its crew stop; the repository and its data stay; It takes the repository's admin, and over MCP an admin token, asarchivedoes. - Turn it back on. Turning off is not asked twice; the way back is offered in the same place instead. On
/asksthe app's row becomes "owner/name is off." with one button, Turn it back on (the repository's own restore,POST /:owner/:name/settings/archive). The MCP answer carriesundo, the exact call (archive {repo, archived: false, dryRun: false}). In the terminal the toast names the key:u. Back on, the app is counted again and the crew may be given work there (turnBackOn). Restore in the repository's settings does the same at any later time. - A re-check says where it stands.
POST …/pulls/:n/checks(page and API) answersCheck queued at the current head: place 3 of 12., and the pull's checks line shows the place while it waits (checks/place.ts, in the order checks were asked; a rebase's check or a pull a red main holds may be passed over). When nothing can be queued the refusal names why: no head, owner suspended, a guest's fork, a head awaiting a writer's approval, or no declared check.