ci: require stable PR gate checks - #345
Conversation
|
Warning Review limit reached
Next review available in: 33 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds a shared CI gate verifier, integrates it into the main and prediction-markets workflows, broadens workflow triggering, and tests successful, skipped, failed, and cancelled job-result handling. ChangesCI gating
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related issues
Possibly related PRs
Sequence Diagram(s)sequenceDiagram
participant SelectedCIJobs
participant ci-gate
participant prediction-markets-gate
participant verify-ci-gate.sh
SelectedCIJobs->>ci-gate: Complete prerequisite jobs
ci-gate->>verify-ci-gate.sh: Pipe serialized needs results
verify-ci-gate.sh-->>ci-gate: Return validation status
SelectedCIJobs->>prediction-markets-gate: Complete prerequisite jobs
prediction-markets-gate->>verify-ci-gate.sh: Pipe serialized needs results
verify-ci-gate.sh-->>prediction-markets-gate: Return validation status
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Closes #344
Change contract
Main PRs always publish stable Monorepo and Prediction Markets gate checks; each gate fails whenever a selected dependency does not succeed, while selector-skipped jobs remain non-blocking.
Acceptance evidence
The new gate jobs run on every pull request, aggregate all conditional jobs, and reject failed or cancelled selected jobs. Main branch protection requires these gates plus the existing Security Summary Report and one fresh approval.
Out of scope
Research snapshot construction, evaluator/MCTS execution, collector deployment, catalog changes, and live execution policy.
Dependency / merge order
None. This is the prerequisite gate before #319.
Focused validation
shellcheck .github/scripts/verify-ci-gate.sh .github/scripts/test-select-rust-ci-scope.shbash .github/scripts/test-select-rust-ci-scope.shgo run github.com/rhysd/actionlint/cmd/actionlint@v1.7.7 .github/workflows/ci.yml .github/workflows/ploy-ci.ymlgit diff --checkRollout / rollback impact
Rollout: main protection is enabled with the three required GitHub Actions checks and fresh approval. Rollback: revert this PR and remove the two required gate contexts before merging the revert.