activate SETTE CI directly on development branches instead of main branch
Currently, SETTE CI is activated only on the main branch with a daily frequency, which is not efficient to detect issues on dev branches.
The idea is to trigger the CI on devs branches before they are merged back into the main branch, either when the developer wants to trigger it for easy branch testing, either when the branch is ready to be merged.
Ressources:
Edited by Guillaume Samson