hub
hub copied to clipboard
mislav
Editing release tag from command line always results as "untagged-XXXXX"
So basically I'm trying to automate my release process by creating a draft "proxy" release and I would like to edit its tag version when I'm about to actually publish the release.
The thing is, I realized that: 1_ When I try to edit anything regarding the release, the tag ends up being something like "untagged-1421c803c66244c71c64" 2_ Can we even change just the tag for a draft release?
STEPS
- So first I apply this (which works):
gabu$ hub release create --draft -m "Proxy release" -t "release/e2e-qa" v0.0.1-proxy
https://github.com/<my_team>/<my_project>/releases/tag/untagged-eb4323448616e25da835
gabu$
✅
✅
- But when I try to edit something (let's say just the title):
gabu$ hub release edit -m "This is such an amazing title" -t "release/e2e-qa" v0.0.1-proxy
gabu$
✅
❌
Which ends up being the original name of the draft release tag that is untagged-eb4323448616e25da835
And when I try to hub release edit again with the latter tag name, it "works" even though it didn't work at the very first edit attempt.
That said, I tried somehow to edit the tag by just adding an additional argument in the end (just trying here...) but again it would result in no changes except for the renaming of the tag to untagged-eb4323448616e25da835.
Which makes me wonder: is this the expected behavior? And most importantly... can we actually change the tag of a draft release by command line?
I feel like I'm missing something trivial here... Thanks in advance!
Thank you for reporting! This seems like it's a bug with GitHub API. I'll update this thread once it's resolved!
can we actually change the tag of a draft release by command line?
No, I don't think this will be possible even with the bug in question fixed. But, you will be able to edit the tag in the web interface. As for the command-line, you could always delete the draft release and create a new one with an updated tag name, containing the original release's title and body.
@mislav Is there a plan to fix this issue? We are running into this issue as part of our release automation effort too (https://github.com/konveyor/move2kube/blob/3edb173611cb806351770003b8ad17eed13aa207/.github/workflows/release.yml#L257).
Sorry that this is biting you all! This issue was reported to the responsible team at GitHub, but I don't know when it will be solved.
Experiencing same issue even today. I am trying to automate our release creations, where I need to keep drafting my release notes(body)-meaning our automation should be able to append the notes to the existing drafted Release. Any updates on this bug, seems it originally reported 3 years ago and still open?
As this is still not fixed, can the upstream bug be followed somehow (is it tracked publicly)?
