ci: avoid triggered-by-schedule and triggered-by-merge builds cancelling each other - #23716
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 9 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe build workflow now separates concurrency groups by ChangesBuild workflow concurrency
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized CI configuration change prevents scheduled and merge-triggered builds from cancelling each other, with no actionable merge-blocking risk remaining after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/merge |
Contributes to rapidsai/build-planning#278
Today, merging a PR while the nightly build is in progress can lead to it being cancelled.
This updates CI configurations to prevent that.