What happens
PR #228 (fix/github-pr-chip-graphql-burn → main, opened 2026-08-06) has produced no Warp CI run at all. The PR was subsequently closed and reopened to re-fire pull_request; still no run.
The only workflow runs on the branch are:
Running Copilot Code Review — dynamic, success
Check Approvals — pull_request_review, conclusion action_required
mergeStateStatus is UNSTABLE and gh pr checks 228 reports "no checks reported on the branch".
Why this looks like a real trigger failure rather than a quiet repo
.github/workflows/ci.yml (workflow name Warp CI, id 274922168) is active and should match:
on: pull_request: with branches: [main, master, "*_release/*"] and types: [opened, reopened, synchronize, ready_for_review] — the PR targets main and has been both opened and reopened.
- No
paths / paths-ignore filter.
- The first job’s guard is satisfied: the PR is not a draft, and the head ref is not
repo-sync/*.
Repository Actions settings are permissive: enabled: true, allowed_actions: "all". No runs are queued or waiting. The workflow-run approve endpoint does not apply (This run is not from a fork pull request or queued by the Actions bot), so this is not a pending fork-approval gate.
What this is NOT
To keep the scope honest: Warp CI last ran on 2026-07-27T15:24:54Z, but the most recent merged PR is #225 at 2026-07-27T11:46 — before that run. No pull request has merged without CI as a result of this. The ten-day gap is the repository being quiet, not evidence of a long-running outage. PR #228 is the first PR since, and it is the one that did not trigger.
Impact
Any PR affected by this cannot show a passing check, so there is no CI signal to merge on. main is not branch-protected, so a merge is still mechanically possible — which makes the missing signal easy to skip past silently rather than being blocked on.
Reproduction
- Open a PR against
main from a branch in this repository.
- Observe
gh api "repos/OpenCoven/cast-codes/actions/runs?branch=<branch>" — no run named Warp CI.
- Close and reopen the PR; re-check. Still none.
What happens
PR #228 (
fix/github-pr-chip-graphql-burn→main, opened 2026-08-06) has produced noWarp CIrun at all. The PR was subsequently closed and reopened to re-firepull_request; still no run.The only workflow runs on the branch are:
Running Copilot Code Review— dynamic, successCheck Approvals—pull_request_review, conclusionaction_requiredmergeStateStatusisUNSTABLEandgh pr checks 228reports "no checks reported on the branch".Why this looks like a real trigger failure rather than a quiet repo
.github/workflows/ci.yml(workflow nameWarp CI, id 274922168) isactiveand should match:on: pull_request:withbranches: [main, master, "*_release/*"]andtypes: [opened, reopened, synchronize, ready_for_review]— the PR targetsmainand has been both opened and reopened.paths/paths-ignorefilter.repo-sync/*.Repository Actions settings are permissive:
enabled: true,allowed_actions: "all". No runs are queued or waiting. The workflow-run approve endpoint does not apply (This run is not from a fork pull request or queued by the Actions bot), so this is not a pending fork-approval gate.What this is NOT
To keep the scope honest:
Warp CIlast ran on 2026-07-27T15:24:54Z, but the most recent merged PR is #225 at 2026-07-27T11:46 — before that run. No pull request has merged without CI as a result of this. The ten-day gap is the repository being quiet, not evidence of a long-running outage. PR #228 is the first PR since, and it is the one that did not trigger.Impact
Any PR affected by this cannot show a passing check, so there is no CI signal to merge on.
mainis not branch-protected, so a merge is still mechanically possible — which makes the missing signal easy to skip past silently rather than being blocked on.Reproduction
mainfrom a branch in this repository.gh api "repos/OpenCoven/cast-codes/actions/runs?branch=<branch>"— no run namedWarp CI.