You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the same Updatecli manifest targeting different branches, Updatecli generates the same temporary branch which results in conflicts.
Today the temporary branch is something like updatecli_<a hash or pipelineID>
Solution you'd like
I would like to include the base branch in the branch such as
master: updatecli_master_<a hash or pipelineID>
main: updatecli_main_<a hash or pipelineID>
Alternatives you've considered
Today's approach is to have different pipelineid per branch but I find it cumbersome to update each manifests, each time I create a new release branch while we have access to the branch information
Anything else?
The fix seems to be simple to do but once apply, Updatecli will generates new pullrequest which IMO is not a big deal but worth mentioning
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When using the same Updatecli manifest targeting different branches, Updatecli generates the same temporary branch which results in conflicts.
Today the temporary branch is something like
updatecli_<a hash or pipelineID>
Solution you'd like
I would like to include the base branch in the branch such as
master:
updatecli_master_<a hash or pipelineID>
main:
updatecli_main_<a hash or pipelineID>
Alternatives you've considered
Today's approach is to have different
pipelineid
per branch but I find it cumbersome to update each manifests, each time I create a new release branch while we have access to the branch informationAnything else?
The fix seems to be simple to do but once apply, Updatecli will generates new pullrequest which IMO is not a big deal but worth mentioning
The text was updated successfully, but these errors were encountered: