Skip to content

Conversation

@jlpedrosa
Copy link

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


release, _, err = c.Repositories.GetReleaseByTag(context.TODO(), c.owner, c.repo, input.Name)
if err != nil {
return fmt.Errorf("getting the existing relase: %w", err)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
return fmt.Errorf("getting the existing relase: %w", err)
return fmt.Errorf("getting the existing relase: %w", err)
Suggested change
return fmt.Errorf("getting the existing relase: %w", err)
return fmt.Errorf("getting the existing release: %w", err)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants