Run CI once per change instead of twice - #51
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow now triggers on pushes to ChangesCI trigger configuration
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change limits CI push runs to main so pull requests run once instead of twice, reducing duplicate CI work and notifications without a demonstrated coverage regression; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
on: push:had no branch filter, so a PR branch matched bothpushandpull_requestand ran the entire suite twice on every push. Visible asfail=2on #47, #48 and #49: two identical backend runs, two failure emails each.Limits the push trigger to
main. PR branches now run once viapull_request,mainruns once viapush. Halves CI minutes and email volume, no loss of coverage.Summary by CodeRabbit
mainbranch. Pull request checks remain unchanged.