updatecli
Replies: 1 comment 7 replies
|
In the meantime, I also tried the following commands: updatecli compose diff --clean
updatecli compose diff --clean=truebut neither performs any cleanup of the UpdateCLI working folder. |
|
If a target is linked to a scm using the scmid then it's reset automatically in diff mode do you already have a branch named like It's only displayed the first time it changes something, following iteration will work from the temporary branch. Could you share your updatecli manifest? |
|
I wonder if you specified the scmid and the actionid if you are using the Golang autodiscovery plugin such ash https://github.com/updatecli/policies/blob/42f76010f7ed647fb5934022a40b7a2ce58ba55e/updatecli/policies/autodiscovery/golang/updatecli.d/default.tpl#L10 and https://github.com/updatecli/policies/blob/main/updatecli/policies/autodiscovery/golang/updatecli.d/_scm.github.yaml |
|
Or just a scmid per target If you use the declarative approach |
|
@olblak I wasn't aware of the branch already being created. After deleting the branch and triggering the GH workflow again, a PR is correctly created. |
If a target is linked to a scm using the scmid then it's reset automatically in diff mode
Is it possible that you already published the changes on a previous iteration?
do you already have a branch named like
updatecli_main_xxxIt's only displayed the first time it changes something, following iteration will work from the temporary branch.
Could you share your updatecli manifest?