Repository navigation
ci: run Check as a signal on ready main PRs - #7623
Conversation
Quest-Claim: 0f89e5cd158a75c1
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
|
Design change: main Check now selects against fetched (Written by GPT-6.1 Sol) |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: 361e6a2
No actionable bugs found. Reusing the existing dispatcher for a non-gating ready-main signal is appropriately small; fetched-base selection, release's full checks, and PR-number cancellation handle readiness, retargeting, and close events without a separate CI implementation. The event-matrix tests cover the policy changes, and read-only token/cache handling is preserved.
Verification limits: static GitHub review of the workflow, selector, cache action, tests, and documentation. I did not run tests or observe live Actions cancellation, and did not independently verify live ruleset or secret configuration.
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the full head 361e6a2 (11 files): the ready-main Check signal, the fetched-base selection, the PR-numbered concurrency group, the rewritten event-policy tests, the doc/comment updates, and the deleted quest.
- Ready-main signal —
check.ymlruns the gate's selection againstorigin/mainfor non-draft main PRs and--allfor release, withclosedstill skipped. - Readiness triggers —
ready_for_reviewandconverted_to_draftadded so a return to draft cancels the in-flight run while release keeps its requiredCheckon every transition. - Concurrency keyed by PR number — verified against GitHub's docs that a merged pull request's
github.refbecomes the merge target branch, so the oldcheck-${{ github.ref }}group would miss the close cancelling the PR's own run. - Tests — the event matrix now sweeps action × base × draft and pins permissions, the absent Environment, and the checkout's
fetch-depth/persist-credentials. - Docs and quest —
nightly.yml,quest.yml,CONTRIBUTING.md,README.md,doc/setup/dev.md, andinfra/README.mdreworded to "signal on ready main PRs";quest/m0/ci/pr-check.mddeleted with no dangling references.
Local bun test sh/gh/queue.test.ts and sh/gh/setup.test.ts pass. Main-PR runs still use the read-only MBX_R2_* pair and name no cache-write Environment, so the secret posture is unchanged from release PRs.
deepseek-v4.1-flash (free via Pullfrog for OSS) | 𝕏
|
No actionable comments were generated in the recent review.
|

Problem
Check skips every main PR, losing the early changed-lane signal before the merge queue runs.
Approach
just ciagainst the fetchedorigin/mainbase for ready main PRs, including readiness transitions and subsequent pushes. Main drafts skip; release PRs retain--all, including drafts.github.ref, also cancels the old run.Impact
Alternatives
Checks
just cipasses in a clean Nix dev shell with mbx active (94 seconds on the final head), including all selected workflow, tooling, documentation, and worker checks.quest check --base origin/mainandgit diff --check origin/mainpass.Review
claude-opus-5-5), medium effort,quest review --base origin/main, round 2.361e6a20eef7164cc6ad19772d5b5dd26a550550. Findings: none.Follow-ups
(Written by GPT-6.1 Sol)