Skip to content

fix(ci-status): report conflicting instead of waiting on a PR GitHub won't build - #104

Merged
devondragon merged 1 commit into
mainfrom
fix/ci-status-conflicting-pr
Oct 13, 2026
Merged

devondragon merged 1 commit into
mainfrom
fix/ci-status-conflicting-pr

Conversation

@devondragon

Copy link
Copy Markdown
Owner

ccm-ci-status now returns conflicting (exit 6) when nothing has registered for the head commit and the PR is CONFLICTING. GitHub can't build the merge ref for such a PR, so its pull_request workflows never start. Before this, --watch waited the full ci_timeout_minutes and auto-ticket parked with "CI never registered", which hid the cause (AIE-351, aiemailpoc PR #881).

Changes:

  • bin/ccm-ci-status: re-reads mergeable in the not-registered path, so it costs one extra gh call there and none when checks exist. It re-reads each poll because mergeability is often UNKNOWN right after a push.
  • skills/auto-ticket/SKILL.md 4c: conflicting → route-and-stop with the conflict as the reason.
  • skills/finish-ticket, skills/merge, README: list the status and say not to wait on it.
  • tests/run.sh: snapshot, watch, and with-checks cases. The snapshot case fails without the script change, and the watch case hangs until the call window ends.
  • tests/every-ticket-since-baseline.diff regenerated for the skill edits. Version 3.20.4.

bash tests/run.sh: 388 passed, 0 failed.

…won't build

GitHub runs no pull_request workflows on a PR that conflicts with its base,
so ccm-ci-status --watch waited out ci_timeout_minutes as not-registered and
auto-ticket parked with "CI never registered" (AIE-351). When nothing has
registered, the script now re-reads mergeability and returns conflicting
(exit 6); auto-ticket stops with the conflict as the reason, and
finish-ticket and merge treat it as the gate's conflict blocker.
@devondragon
devondragon merged commit ba8b642 into main Oct 13, 2026
2 checks passed
@devondragon
devondragon deleted the fix/ci-status-conflicting-pr branch October 13, 2026 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant