Repository navigation
ci(release): add workflow_dispatch to release-please workflow - #1512
Conversation
Allows manual triggering when the autorelease pending label gets stuck (e.g. release-please aborts due to untagged merged PR confusion).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 13 minutes and 39 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
|
Failed to generate code suggestions for PR |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 1 file
Requires human review: Adding workflow_dispatch to a CI/CD workflow changes the deployment infrastructure, which is high-risk. Manual triggers can affect production releases and require human oversight.
Re-trigger cubic
|
This branch was successfully deployed
1 participant
Summary
workflow_dispatchtrigger to release-please workflowautorelease: pendingstuck on a previously-merged PRWhy
Release-please aborted today with
⚠ There are untagged, merged release PRs outstandingbecause PR #1508 hadautorelease: pendinglabel still set after v2.18.0 was released. Fixed the label on #1508; thisworkflow_dispatchmakes it easy to re-trigger without needing a dummy commit.Summary by cubic
Enable manual runs of the
release-pleaseworkflow by adding aworkflow_dispatchtrigger. This lets us re-run releases whenautorelease: pendinggets stuck or whenrelease-pleaseaborts due to untagged merged PRs, without a dummy commit.Written for commit 2ae9bdb. Summary will update on new commits.