Landing: 'land when checks pass', and 'land now' over checks issue #261 closed: completed andymccall opened this 17 days ago · 0 comments

Asked by Andy (2026-10-18): proposals sometimes need to land before their checks finish, e.g. runners down while the fix waiting in the queue needs checks on those same runners.

Land when checks pass (auto-land): anyone who may land sets it on the proposal (button beside Land; API POST /proposals/{n}/auto-land, DELETE to turn off; oh proposal land --when-ready). It lands once the required checks pass on the current projected state and no other blocker remains, as the person who set it, if they still may land. A push that adds changes re-runs the checks and it waits again; failing checks turn it off with a note on the timeline; anyone who may land can turn it off. Shown on the proposal and in the list.

Land now over checks (override): repository maintainers and admins may land while required checks are pending or failed, with a reason (required). It skips only the checks: approvals, code owners, changes requested, drafts and the trust policy still apply. Audited (proposal.land_over_checks), on the timeline and the landed banner ('landed over checks by X: runners down'), and in the API ({"over_checks": "reason"} on land; oh proposal land --over-checks REASON).

Decided by Andy: maintainers, checks only; auto-land stays on across pushes, re-evaluated.