ci: disable carryforward flags to flush stale data#543
Conversation
Stale `carryforward` flags from a previous per-crate flag config are inflating the session count and causing premature codecov status checks. Disabling carryforward temporarily so a clean CI run establishes fresh baseline data for the current flags.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA configuration change to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v0.42-dev #543 +/- ##
=============================================
- Coverage 66.87% 65.96% -0.92%
=============================================
Files 313 311 -2
Lines 64753 64586 -167
=============================================
- Hits 43305 42602 -703
- Misses 21448 21984 +536
|
This reverts commit e6e6964.
This reverts commit e6e6964.
Stale carryforward flags from a previous per-crate flag config are inflating the session count and causing premature codecov status checks. Disabling carryforward temporarily so a clean CI run establishes fresh baseline data for the current flags.
Summary by CodeRabbit