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
Add use-existing-release option to upload functionality
This makes it possible to add the release packages to an existing release instead of creating a new release.
This is useful when a release is used to trigger the helm package and upload.
Copy file name to clipboardexpand all lines: README.md
+1
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,7 @@ Flags:
85
85
--release-name-template string Go template for computing release names, using chart metadata (default "{{ .Name }}-{{ .Version }}")
86
86
--release-notes-file string Markdown file with chart release notes. If it is set to empty string, or the file is not found, the chart description will be used instead. The file is read from the chart package
87
87
--skip-existing Skip upload if release exists
88
+
--use-existing-release Add pacakges to exisiting release instead of creating new release
88
89
-t, --token string GitHub Auth Token
89
90
--make-release-latest bool Mark the created GitHub release as 'latest' (default "true")
90
91
--packages-with-index Host the package files in the GitHub Pages branch
Copy file name to clipboardexpand all lines: doc/cr_upload.md
+1
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ cr upload [flags]
30
30
--release-notes-file string Markdown file with chart release notes. If it is set to empty string, or the file is not found, the chart description will be used instead. The file is read from the chart package
31
31
--remote string The Git remote used when creating a local worktree for the GitHub Pages branch (default "origin")
32
32
--skip-existing Skip upload if release exists
33
+
--use-existing-release Add pacakges to exisiting release instead of creating new release
0 commit comments