ci(nightly): stop tagging the repo for every nightly build#652
Conversation
|
Warning Review limit reached
Next review available in: 25 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: Path: .coderabbit.yaml 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 |
The
/tagspage is cluttered withnightly-*anddev-*git tags, drowning the realv*releases.Cause:
build_dev.ymlcreated a GitHub Release (viancipollo/release-action) per nightly — and a Release requires a git tag. The ray job did it again with a-raysuffix, so 2 git tags per night. Thecleanup-old-dev-releasesjob only prunednightly-*releases (notdev-*, and tag deletion was best-effort), so tags accumulated.Fix: nightlies are now image-only artifacts. Removed both
Create development releasesteps and the cleanup job. The nightly still builds and pushes to ghcr withnightly,dev-latest, andnightly-YYYYMMDD-shaDocker tags (traceability preserved); it no longer writes any git tag or Release. Also droppedcontents: write(least privilege — no longer needed).Result:
/tagswill only ever show realv*releases going forward. A separate one-time purge will remove the existingnightly-*/dev-*tags.