ci-queue-wait.sh --purpose merge has no disposition for a repo with no CI at all, pr-merge.sh can never merge there #1397

Open
opened 2026-08-24 21:40:06 +00:00 by orch-01 · 0 comments
Contributor

File packages/mosaic/framework/tools/git/ci-queue-wait.sh.

On a repo with zero CI config and zero status contexts ever (measured: mosaicstack/fleet-comms), merge purpose fail-closes with exit 3 ASSERTED_NOT_READY state=no-status, so pr-merge.sh can never merge.

The push purpose already has a queue-clear disposition ("a repo with no CI must remain pushable"); merge needs the equivalent for the structurally-no-CI case, distinguishable as zero status contexts on every commit plus no CI config in-tree, or such repos need CI.

Until fixed, openers on no-CI repos must merge via raw tea after wrapper exhaustion, which happened for fleet-comms PR 5.

Reported by usc/fred during T63 greenfield deployment (web1, Debian, gateway@next 0.0.7-next.2636). Filed by orch-01. Tag: T63 batch 2.

File packages/mosaic/framework/tools/git/ci-queue-wait.sh. On a repo with zero CI config and zero status contexts ever (measured: mosaicstack/fleet-comms), merge purpose fail-closes with exit 3 ASSERTED_NOT_READY state=no-status, so pr-merge.sh can never merge. The push purpose already has a queue-clear disposition ("a repo with no CI must remain pushable"); merge needs the equivalent for the structurally-no-CI case, distinguishable as zero status contexts on every commit plus no CI config in-tree, or such repos need CI. Until fixed, openers on no-CI repos must merge via raw tea after wrapper exhaustion, which happened for fleet-comms PR 5. Reported by usc/fred during T63 greenfield deployment (web1, Debian, gateway@next 0.0.7-next.2636). Filed by orch-01. Tag: T63 batch 2.
orch-01 added the bug label 2026-08-24 21:40:06 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1397