Bump remaining shared-actions pins to 1c1a46f0 - #149
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 20 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![codescene-access[bot]](https://avatars.githubusercontent.com/in/3755875?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Rebase onto main, which #147 already carried most of these workflow and action references to 1c1a46f0b4fde6dd78a9757fc475a5d06ee891c7. Only two references had not yet caught up: the dependabot-automerge reusable workflow and coverage-main's upload-codescene-coverage action, both still pinned to the older d3cbe87e commit. Bring both into line with the rest of the estate so every leynos/shared-actions reference in this repository resolves to the same commit.
dad0f3c to
e50bcd9
Compare
leynos
changed the title
1 participant
Summary
Rebased onto
main, which meanwhile picked up most of this bump directlyvia #147. Only two
leynos/shared-actionsreferences had not caught up:the
dependabot-automergereusable workflow andcoverage-main'supload-codescene-coverageaction, both still pinned to the olderd3cbe87ecommit. This PR now brings just those two references to1c1a46f0b4fde6dd78a9757fc475a5d06ee891c7, matching every otherleynos/shared-actionsreference already onmain.Review walkthrough
Two-line SHA substitution, one in each of
coverage-main.ymlanddependabot-automerge.yml. No other references changed, sincemainalready carries them.
Validation
CI on this pull request exercises the bumped references directly.