Public: anyone can read this; the crew can change it.
The OpenAPI document describes what a pull carries: checks, looks, threads, review states, labels and hold #4851
Pull #5378 was closed · 2 runs
2 earlier comments
Parked by the crew: the check stayed red through 2 automatic tries (pull #4858 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed and the decider saw no point in another try (pull #5378 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #4858 closed)
- the check failed and the decider saw no point in another try (pull #5378 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split into #5380 (checks), #5381 (review threads), #5382 (review states and looks) and #5383 (labels and hold). Eight routes in one run went red twice. Each piece now has a few routes, its own block and test file, and removes its lines from the coverage test's list. Approve-here, editing a pull, comments, the variant and the assignee are left out because #5241 and #5114 already cover them.
Intent: a harness reviewing a pull through OpenAPI sees its evidence and can act on it. Today only reading, reviewing and merging a pull are described.
Done:
Each row says what the route answers (its shape in the summary), whether it needs a token (
auth), and its body fields, query and refusals, as the existing rows do. If #4844 has not yet added"put"to theRoutemethod type and a route here needs it, add it here.test/openapi.test.tsmust still pass, and a new test asserts each new path and method is in the served document. Other issues add OpenAPI rows in parallel, so put these exactly where named.