probe: does a fresh cargoless PR schedule CI? #100

Closed
schema-migration-steward wants to merge 1 commit from probe-ci into main

Diagnostic only — will be closed. Every run on PR #99 since 19:49 UTC is created with all jobs already SKIPPED and no runner ever claims them. This branch is origin/main plus one empty commit. If its CI schedules, the problem is scoped to PR #99; if it also skips, cargoless actions scheduling is broken repo-wide.

Diagnostic only — will be closed. Every run on PR #99 since 19:49 UTC is created with all jobs already SKIPPED and no runner ever claims them. This branch is origin/main plus one empty commit. If its CI schedules, the problem is scoped to PR #99; if it also skips, cargoless actions scheduling is broken repo-wide.
probe: does a fresh cargoless PR schedule CI?
Some checks are pending
ci / build (pull_request) Waiting to run
ci / test (pull_request) Waiting to run
ci / lane policy mutation proof (pull_request) Waiting to run
ci / fmt (pull_request) Waiting to run
ci / clippy (pull_request) Waiting to run
ci / rust-analyzer latency harness (S1 / AC#2) (pull_request) Waiting to run
5cc3fc593e
Diagnostic only. Every run on PR #99 since 19:49 UTC is created with all
jobs already status=5 (SKIPPED) — no runner ever claims them. The
workflow is byte-identical to main, the PR is mergeable, concurrency
groups are unique per-sha, and the coalescer only touches tf-mv.

This branch is origin/main plus one empty commit. If its PR schedules,
the problem is scoped to PR #99. If it also skips, the repo's actions
scheduling is broken and needs an operator.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Some checks are pending
ci / build (pull_request) Waiting to run
ci / test (pull_request) Waiting to run
ci / lane policy mutation proof (pull_request) Waiting to run
ci / fmt (pull_request) Waiting to run
ci / clippy (pull_request) Waiting to run
ci / rust-analyzer latency harness (S1 / AC#2) (pull_request) Waiting to run

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
triform/cargoless!100
No description provided.