-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag release with commit hash of the tip of current branch #42
Conversation
At present, the tip of the default branch is tagged with the release. This is not ideal if we want to make releases out of non-default branches. Use the current commit ID as the input when invoking `cr upload` so that the releases are tagged correctly. Signed-off-by: Bharat Kunwar <bharat@stackhpc.com>
Ping, anyone care to look at this? |
/cc @davidkarlsen |
Thanks for approving @davidkarlsen, when will this be incorporated into a release? |
@davidkarlsen when will this be merged? |
Merged, I believe @unguiculus has some more changes he wants in before a release. |
@davidkarlsen can we tag this release as v1.0.1 then tag @unguiculus's change as v1.0.2 when its ready? It would really help. Cheers. |
Sorry, I mixed the chart-testing and chart-releaser (helm/chart-testing#269). |
At present, the tip of the default branch is tagged with the release. This is not ideal if we want to make releases out of non-default branches. Use the current commit ID as the input when invoking `cr upload` so that the releases are tagged correctly. Signed-off-by: Bharat Kunwar <bharat@stackhpc.com>
At present, the tip of the default branch is tagged with the release instead of the branch target for release. This is not ideal if we want to make releases out of non-default branches. Use the current commit ID as the input when invoking
cr upload
so that the releases are tagged correctly.