On an autonomous repository landIfGreen sends every green pull to the crew's reviewer and lands it on approval. A person has no plain way to say "not this one yet" (for example while a second review is under way). Today the only hold is a database trigger that keeps the check from going green, which is a workaround.
[ ] a person who can write the repository can hold a pull and release it; a held pull is never sent to the reviewer by rule and never lands by rule; a person's own merge still works
[ ] the hold is visible on the pull, the change page and the map, with who held it and why (one line)
[ ] reachable: a button on the change page, PUT/DELETE …/pulls/:n/hold over the API, and an MCP tool, dry run by default
[ ] a hold does not raise an ask for the person who set it
[ ] refusing tests: a reader, a stranger and an agent cannot hold or release; a held green pull with an approving review does not land
Pillar: P0 Trust.
On an autonomous repository
landIfGreensends every green pull to the crew's reviewer and lands it on approval. A person has no plain way to say "not this one yet" (for example while a second review is under way). Today the only hold is a database trigger that keeps the check from going green, which is a workaround.PUT/DELETE …/pulls/:n/holdover the API, and an MCP tool, dry run by default