Repository navigation
Conversation
|
Warning Review limit reached
This review includes 1 billable file and costs up to $0.25.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 47 minutes for your next included review. View limit details
|
Bundle ReportBundle size has no change ✅ |
- Evaluate PRs into any base except Development, not only main - Refresh red checks on every open PR after a Development push
c744a9f to
ba20329
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #391 +/- ##
==========================================
- Coverage 49.45% 49.45% -0.01%
==========================================
Files 1232 1232
Lines 62435 62435
Branches 8748 8748
==========================================
- Hits 30876 30875 -1
Misses 30125 30125
- Partials 1434 1435 +1
Flags with carried forward coverage won't be shown. Click here to find out more. |
The advisory Development merge check only looked at PRs targeting
main, in both places it runs:pull_requesttrigger was limited tobranches: [main], so a PR opened stacked on another feature branch never got a verdict.base: main, so a PR retargeted onto another branch kept its old red result after it landed in Development. This happened on VPR-244 feat(effort): set CAHFS report unit for 072200 on harvest #383 after it was stacked on VPR-255 feat(effort): clean up zero-effort data when closing a term #385.Changes:
pull_requestnow runs for any base exceptDevelopment(a PR into Development is never in Development before it merges).