Open philnewm opened 1 week ago
MAIN_BRANCH variable is currently used through the whole workflow. This could be changed to DESTINATION_BRANCH
We could then reuse the same actions for different target branches e.g. when we make release of previous minor version.
Then the Trigger could assign main to the DESTINATION_BRANCH
main
No response
Is there an existing issue for this?
Please describe the enhancement you have in mind and explain what the current shortcomings are?
MAIN_BRANCH variable is currently used through the whole workflow. This could be changed to DESTINATION_BRANCH
We could then reuse the same actions for different target branches e.g. when we make release of previous minor version.
How would you imagine the implementation of the enhancement?
Then the Trigger could assign
main
to the DESTINATION_BRANCHAre there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response