ci: stop re-running validation workflows on push to main#834
Conversation
The merge queue already validates everything before merging. Remove push-to-main triggers from validation-only workflows: - e2e.yaml: e2e tests + compat tests (validation) - lint.yaml: Go/Python/protobuf linters + typos (validation) - python-tests.yaml: pytest matrix across versions/OSes (validation) Workflows that remain on push to main are release/deploy actions: - build-images.yaml: builds + pushes container images to quay.io - documentation.yaml: deploys docs to GitHub Pages - trigger-packages.yaml: triggers package index rebuild All three validation workflows retain workflow_dispatch for manual runs.
|
Warning Review limit reached
More reviews will be available in 16 minutes and 30 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 rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. 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 (3)
✨ 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 |
2 participants
Problem
Every merge to
mainre-runs all validation workflows (e2e tests, linters, python tests) even though the merge queue already validated them. This wastes CI resources and clutters the commit status.Changes
Remove
pushtriggers from validation-only workflows:e2e.yamlpush: mainlint.yamlpush: main, release-*python-tests.yamlpush: main, release-*What still runs on push to main
These workflows perform release/deploy actions that can only happen after merge:
build-images.yamllatesttagdocumentation.yamltrigger-packages.yamlSafety net
All three validation workflows retain
workflow_dispatchfor manual runs if needed. The merge queue provides full validation coverage before any code reachesmain.