feat(cascading): option to bypass non-latest minor branch

[kpanot]

Proposed change

Option to bypass non-latest minor branch on cascading bot

Related issues

- No issue associated -

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c4a10be. 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

---

✅ Successfully ran 11 targets

• nx run-many --target=test-int --parallel 3
• nx run-many --target=build --projects=eslint-plugin --parallel 3
• nx run-many --target=test-e2e --parallel 3
• nx run-many --target=publish --parallel 3 --nx-bail --userconfig .verdaccio/conf/.npmrc-logged --tag=latest --@o3r:registry=http://127.0.0.1:4873 --@ama-sdk:registry=http://127.0.0.1:4873 --@ama-terasu:registry=http://127.0.0.1:4873 --@o3r-training:registry=http://127.0.0.1:4873
• nx run-many --target=documentation --parallel 3
• nx affected --target=test --parallel 3 --cacheDirectory=D:\a\otter\otter/.cache/jest --base=remotes/origin/main --collectCoverage
• nx run ama-sdk-schematics:build-swagger
• nx run-many --target=build --parallel 3
• nx affected --target=test --parallel 3 --cacheDirectory=/home/runner/work/otter/otter/.cache/jest --base=remotes/origin/main --collectCoverage
• nx affected --target=lint --parallel 3 --base=remotes/origin/main --configuration ci
• nx run-many --target=build-swagger --parallel 3

---

Sent with 💌 from NxCloud.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.31%. Comparing base (0042a21) to head (c4a10be).
Report is 10 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[matthieu-crouzet]

Why are not we deprecating it ?
If we want to be able to re-use that part of the code for another platform,
we may extract that part in a dedicated package
else it seems to be stricly done for GitHub and then we should deprecate this proprety

[kpanot]

I did not deprecate this option because I think that as the cascading is already today platform agnostic (event if it is implemented only for Github) and this option still make sense for supporting platform, it would be weird to remove it in 1 year to follow the unique implementation to potentially seeing it reappear after a while because of a new implementation.
It made more sense for me to keep it and warn the Github users instead, but I am OK to change if needed.

PS: To implement another platform support, there is no need to extract code, it's the bot that should switch the implementation according to the received message. So today it is already ready to support multi platform as it is

[cpaulve-1A]

We should probably not activate it for us

[kpanot]

Why ? I was thinking that it is actually the issue we have today with the non-removed prerelease branches and the policy supporting only the latest minor of each major?

Saw a configuration I would discuss of

[vscaiceanu-1a]

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?

[kpanot]

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?