Currently even if the option --skip-existing is not set, upload will fail when the release exists.
This PR makes the behaviour more consistent, when the release was externally created, chart-release upload will upload the charts/assets to the existing release.
This enables repositories that collocate the code and the deployments to have a unified release.
Currently even if the option --skip-existing is not set, upload will fail when the release exists.
This PR makes the behaviour more consistent, when the release was externally created,
chart-release upload
will upload the charts/assets to the existing release.This enables repositories that collocate the code and the deployments to have a unified release.
cc: @Koenkk