fix(ci): repoint io-triage to wave-foundation-public mirror - #41
Conversation
The public->private uses: reference produces a startup_failure with no jobs, no logs, and no visible check - it is invisible on issue events. Repoint all three pointers (uses/scripts_repo/scripts_ref) to the published mirror at the pinned SHA.
|
Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI. |
|
ⓘ Qodo reviews are paused because your workspace is out of credits. Ask your workspace admin to add credits to resume reviews. Manage billing |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @yakimoto, this account has used its review budget of 2,500,000 diff characters for the last 7 days.
You can request another review in 1 day and 4 hours by commenting @sourcery-ai review.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_59fb38b3-1e48-4392-ada0-c28f063686a7) |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideFixes issue triage startup failures in this public repository by aligning all three workflow and script-source references with the public mirror, pinned to the same commit; reviewers should verify a successful or non-startup-failure run after an issue event. File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📜 Recent review details⏰ Context from checks skipped due to timeout. (4)
🧰 Additional context used🪛 zizmor (1.29.0).github/workflows/issue-ops-triage.yml[warning] 19-19: permissions without explanatory comments (undocumented-permissions): needs an explanatory comment (undocumented-permissions) 🔇 Additional comments (3)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe issue triage job now uses the public ChangesIssue triage workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🔵 Low · up to This change restores issue triage by switching the workflow and scripts to a pinned public mirror. A failed or cancelled edited-issue run could still leave stale approval labels because cleanup happens after triage, so the PR is mergeable with explicit owner awareness and follow-up. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description clearly explains the problem, cause, fix, affected references, validation approach, and scope. It does not include the template's explicit Type of change or Checklist sections, but the required change information is otherwise complete and on topic. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Code Review ✅ ApprovedFixes issue-ops triage on this public repo by repointing the reusable workflow OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
ApprovabilityVerdict: Would Approve Macroscope's review found this PR approvable — This is a narrowly scoped CI fix that repoints an existing issue-triage workflow and its runtime scripts to a matching immutable commit in the public mirror. It preserves the existing triggers, permissions, secrets, and configuration while allowing the previously failing workflow to run. Not approved because:
Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more. |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
1 participant
Repoints
.github/workflows/issue-ops-triage.ymlfrom the privatewave-av/wave-foundationrepo to the published public mirrorwave-av/wave-foundation-public.Symptom. This is a public repo.
Actions -> issue-ops-triageshows 15 consecutivefailureconclusions on theissuesevent (most recent 2026-08-30). Every run fails with zero jobs and zero logs - it never showed as a check anywhere, because it is not triggered onpull_request, it is triggered onissues, so there was no PR check rollup to notice it in either. Issue triage has effectively never worked on this repo.Cause. A public repo cannot
uses:a reusable workflow hosted in a private repo (wave-av/wave-foundation). GitHub Actions refuses the job before it starts (startup_failure) - no job list, no log output, nothing actionable in the UI beyond the bare failed run.Fix - three pointers, all required together:
uses:->wave-av/wave-foundation-public/.github/workflows/io-triage.yml@f63b91566ab311b09599db6195da8c353cab1f69scripts_repo:->wave-av/wave-foundation-publicscripts_ref:->"f63b91566ab311b09599db6195da8c353cab1f69"scripts_repo/scripts_refare not optional companions touses:-io-triage.ymldoes not embed its scripts; it does asparse-checkoutofscripts/issue-opsfromscripts_repoatscripts_refand executes them at runtime. Moving onlyuses:clears thestartup_failureand then fails one step later on a checkout of a private repo the caller repo token cannot read. All three must move together, to the same pinned SHA.This exact fix is proven green on the pilot repo (
wave-av/adk, first success in 9 runs all-time, 2026-09-01T13:07) after all seven scripts in the io-triage dependency closure were published to the mirror.Verify after merge (by run outcome, not the PR check rollup - this workflow does not run on
pull_request):Expect a
success(or at minimum nostartup_failure) on the nextissues: opened/editedevent.Change is scoped to exactly these three YAML values; nothing else in the file was touched.
Note
Low Risk
Single-file CI pointer update with no application or auth logic changes; same bot app secrets and issue permissions as before.
Overview
Fixes issue-ops triage on this public repo by repointing all three dependencies on the private
wave-av/wave-foundationworkflow/scripts to the public mirrorwave-av/wave-foundation-public, pinned atf63b91566ab311b09599db6195da8c353cab1f69.The reusable job
uses:path, plusscripts_repoandscripts_ref(used at runtime for sparse-checkout ofscripts/issue-ops), must all move together—public repos cannot call reusable workflows in private repos, which caused immediatestartup_failurewith no logs.No other workflow inputs, permissions, or secrets change.
Reviewed by Cursor Bugbot for commit 7841ec8. Bugbot is set up for automated code reviews on this repo. Configure here.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by Sourcery
Repoint issue-operation triage to the pinned public workflow and script mirror so issue events can execute successfully.
Bug Fixes:
CI: