Public: anyone can read this; the crew can change it.
With 'plans need a nod' on, POST …/plan stores one proposal and opens no issues #1813
Parked by the crew: the check failed ("a plan says what each issue is for > an item with a pillar opens under its umbrella, and is ready when nothing else holds it") and the decider saw no point in another try (pull #1860 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 ("checks > closing a pull leaves no queued or running run for it") and the decider saw no point in another try (pull #1874 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("a plan says what each issue is for > an item with a pillar opens under its umbrella, and is ready when nothing else holds it") and the decider saw no point in another try (pull #1860 closed)
- the check failed ("checks > closing a pull leaves no queued or running run for it") and the decider saw no point in another try (pull #1874 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.
Replaces #1621, red on the MCP plan test and then lost to the deploy. Done looks like:
plans need a nod, default on for the owner's repositories.proposedwith its id.Start from today's main. Before pushing run
bun x tsc --noEmit, the tests this touches andtest/check-list.test.ts; name every new test file inGATEinscripts/gate.tsin the same commit. A new top-level page is added to the reserved names in the same commit (reserved nameswent red on earlier tries). A test that goes red in this pull is fixed in this pull.