ci: rebuild hourly central PR maintenance on current develop - #326
ci: rebuild hourly central PR maintenance on current develop#326seonghobae wants to merge 6 commits into
Conversation
|
Warning Review limit reached
Next review available in: 4 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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 |
|
@coderabbitai review |
|
| cancel-in-progress: false | ||
|
|
||
| permissions: | ||
| actions: write |
| permissions: | ||
| actions: write | ||
| checks: read | ||
| contents: write |
Purpose
Rebuild the repository-local hourly pull-request maintenance caller from exact protected
develop@d6c6665163eabe1b5eca80556c6963bafd6b2625, independently of stale multi-purpose PR #121. The caller reuses the centrally governed scheduler by immutable commit rather than copying review, branch-update, and merge logic into mightyETL.TDD evidence
The test-only RED head
104f06fc576f216bf3dca2df00d247ed5c18d697reached the intended contract boundary on macOS, Ubuntu, and Windows. Maven compiled production and test code, ran 325 tests, and failed onlyHourlyPrMaintenanceCallerTestbecause.github/workflows/hourly-pr-maintenance.ymldid not exist.Current GREEN head:
f76b19bda972f1c826cd2d70c7c3b1dcb6ce08d0.Bounded implementation
workflow_dispatch;ContextualWisdomLab/.github/.github/workflows/pr-review-merge-scheduler.yml@6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba;develop, scans at most 100 pull requests, requests missing current-head reviews, updates eligible branches, and uses policy-governed direct-or-auto merge;actions,checks,contents,id-token, andpull-requestspermissions required by the reusable workflow;COPILOT_GITHUB_TOKEN,NVIDIA_NIM_API_KEY, or independent reviewer credentials;CHANGELOG.md;Scope boundary
This PR replaces only the hourly PR-maintenance slice of #121. It does not supersede #121's distinct product-development, CI, SBOM, coverage, or supply-chain work.
Merge gate
Ready for independent review. Merge only after exact-head CI, SAST, dependency, SBOM, security checks, zero unresolved findings, and repository approval policy are satisfied. The
automerge-workflowlabel authorizes review of the workflow-file change; because repository auto-merge is disabled, the centrally governed direct-or-auto scheduler may perform the final expected-head direct merge only after every policy gate passes.