feat: add rankweave-hourly-review-repair.yml caller - #1289
Conversation
RankWeave's own hourly loop previously called pr-review-fix-scheduler.yml
cross-repository at a pinned commit SHA. That reusable workflow's
same-repository trusted-source hardening (github.repository ==
ContextualWisdomLab/.github) rejects any such caller, so RankWeave's
review-feedback repair job has failed with zero jobs scheduled
("workflow file issue") for as long as the hardening has been in place.
Add a central caller matching the pattern already proven for
fast-mlsirm, DiskSage, and every other product repository: a same-repo
`uses: ./.github/workflows/pr-review-fix-scheduler.yml` reference on a
dedicated hourly cron, targeting ContextualWisdomLab/RankWeave. A
companion RankWeave PR removes the now-dead local job.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K8VWdPkLwNYHGAKWowfueJ
|
Warning Review limit reachedNext included review available in 44 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
|
Exact-head formal review request for 7684f88. Please inspect the complete changed-file diff, with emphasis on hourly caller scope, credentials, schedule/concurrency, and exact-head repair boundary. Publish a substantive Reviews API verdict tied only to this exact SHA, including security/control-plane impact, test gaps, and residual uncertainty. Do not reuse predecessor-head evidence or failed provider checks as source findings. @opencode-agent |
Exact-head Strix RCA — 7684f88The failed required Strix run was inspected from its job log. It did not report a source vulnerability: the run failed closed because the provider/runtime path was unavailable.
This is provider/runner infrastructure evidence for the current head, not a source finding in the RankWeave caller. The PR remains |
Summary
hourly-commercialization-loop.ymlpreviously calledpr-review-fix-scheduler.ymlcross-repository at a pinned commit SHA (ContextualWisdomLab/.github/.github/workflows/pr-review-fix-scheduler.yml@21397126d708d2d536ccc1d68b0d333653ce9315).pr-review-fix-scheduler.yml's current main hardens a same-repository trusted-source check (github.repository == ContextualWisdomLab/.github, seedocs/doctoringcomments already in the file). A cross-repository caller can never satisfy that check, so every RankWeave hourly run has failed with zero jobs scheduled ("workflow file issue") for as long as the hardening has been in place -- 19+ consecutive failures observed over 18+ hours in RankWeave's own Actions history..github/workflows/rankweave-hourly-review-repair.yml, matching the pattern already proven forfast-mlsirm,DiskSage, and every other product repository: a same-repouses: ./.github/workflows/pr-review-fix-scheduler.ymlreference on a dedicated hourly cron (minute 33, unused by any existing caller), targetingContextualWisdomLab/RankWeave, with a two-hour same-head retry floor matching the dominant convention across callers.hourly-nvidia-nim-review-repair.yml's exact-head focused quality gate (2/2/3 reference counts, matching every existing caller).repair-review-feedbackjob from RankWeave's own hourly loop.Test plan
Generated with Claude Code
https://claude.ai/code/session_01K8VWdPkLwNYHGAKWowfueJ