Open kpanot opened 1 week ago
CI is running/has finished running commands for commit c4a10be22ccd6478887df5a77bcdb6af1a42e16e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
Sent with 💌 from NxCloud.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 74.31%. Comparing base (
0042a21
) to head (c4a10be
). Report is 10 commits behind head on main.
:white_check_mark: All tests successful. No failed tests found.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Is there a case where we want to skip non-latest minors? Wouldn't this create incoherence and confusion among the different branches / code levels?
Not sure to understand why. As for the policy, we considered the latest minor branches as supported/maintained branches. Which mean that all the other branches are considered as archived (if they are not destroyed). When we cascade, we want to do it only on the considered branched automatically, why would it create "incoherence" to skip unmaintained branches?
Proposed change
Option to bypass non-latest minor branch on cascading bot
Related issues
- No issue associated -