Open amalgamm opened 1 year ago
@davidkarlsen can you have a look at this pr?
I just realized that my PR is a duplicate of this one, and this one is better as it fixes the tests. https://github.com/helm/chart-releaser/pull/336
Can we have someone take a look at this PR please ?
does anyone can provide some manual tests on this? @amalgamm @gaelgatelement and show the logs and maybe the ci job
I'm using this fork in our own CI runs : https://github.com/vector-im/ess-starter-edition-core/actions/runs/6624187779
thanks @gaelgatelement @amalgamm can you rebase and fix the lint issues?
tested on my side and seems to work fine :)
Hi! I just run into the issue this PR fixes, it'd be cool to have it merged!
@cpanato I think I fixed the lint. Sorry it took so long
Did you test the case with PackagesWithIndex
set as well? not sure if will change any behavior
Did you test the case with
PackagesWithIndex
set as well? not sure if will change any behavior
I didn't but I think this case is covered by tests
please merge
Any way to get this merged? @cpanato
Sorry to tag again @cpanato but I'm running into the described issue as well and am hoping to see this merged. Thank you!
I did a test using the latest chart-release and two chart updates and i see one push: https://github.com/cpanato/testing-ci-providers/actions/runs/9764682879/job/26953586398
Is this PR trying to update as well? If so, are we good, or am I missing something else?
cc @davidkarlsen
Resolves the problem mentioned in this PR
Lets say you want to upload more than one release and place it near the index file. After the first push your second push will be rejected with an error "Updates were rejected because a pushed branch tip is behind its remote". So either you need to pull changes before push another release or push all releases once in the end of upload action.
In case of pulling changes and pushing every release separately you'll face github will launch as many "pages build and deployment" actions as there are new releases you want to upload. All except one will be canceled, but the list of actions will look like a mess.
So the most efficient way is to make single push in the end of upload.