The open-issue ceiling

Past a number of open issues the planner stops opening more, so the pile shrinks before it grows again. It is off until the owner (a person who administers the repository, never an agent) sets it: any whole number from 1 to 100000, or 0 for off again. The count is every open issue, the ones behind the Later gate too, which no builder starts: set it above what the gate holds, or the pile cannot shrink under it.

Set it. On /:owner/:name/queue the row "Open-issue ceiling" shows the number and, under it, why; the owner types a new one and presses "Set the ceiling". In the terminal, the Queue screen takes c to set it and r to resume. Setting it ends any resume. planner.ceiling is heard by the admins.

Held. Over the ceiling the repository's planner opens no issue, adds no plan and starts no run, and says why in the words of the row ("the planner is held by the open-issue ceiling: 151 issues are open, past the ceiling of 150"). The API answers 409 planner_ceiling with the same words. /flow lists every repository held, and the engine's tick line says it each time the planner is not asked (planner not asked why="the planner is held by the open-issue ceiling: …"). People, builders and reviewers are never held. When closes bring the count back under it, the planner carries on by itself.

Resume. "Resume the planner for one plan" (r in the terminal) lets the planner open the next 12 issues past the ceiling, once: the allowance is the open count then plus 12.

What still goes in.

itself, so it is a convention, not proof; the ceiling bounds it instead of trusting it: such issues take the pile at most 12 past the ceiling.

Not done: a limit for builders or people, a ceiling per label, and checking what an Evidence: line cites.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs