ci: re-pin shared workflow callers to CodesWhat/.github main 11004e4 - #320
Conversation
The shared repo promoted #36 to main (CodesWhat/.github#37). Trigger and input surface are unchanged between the pins; the bump picks up the main-is-released fixes (release-shaped tag required, prerelease detection corrected, no drift report in the merge-to-tag window) and the starchart doc comment that no longer recommends release: [published].
|
Deployment failed for project sockguard-website with the following error: Learn More: https://vercel.com/codeswhat?upgradeToPro=build-rate-limit |
|
Warning Review limit reached
Next review available in: 39 minutes Limit 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. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
CodesWhat/.github promoted #36 to main at 11004e42d7d19e86eb3b7777c467ec9522b784e1 (CodesWhat/.github#37). Bumps both reusable-workflow pins from a66a777304d657a90161a8859dbc0dfa7d5020f7.
Drop-in: the
on:block trigger and input surface are identical between the two SHAs (verified upstream by the ops lane). What the bump picks up:my-tagas prereleases, and stops reporting drift for the window between a promotion merge and the tag push.release: [published], matching the dispatch-only caller from ci(starchart): make the refresh dispatch-only and read the branch from the ref #319.No caller-side input changes needed; #319 already moved starchart.yml to
branch: ${{ github.ref_name }}.