Open inktomi opened 4 years ago
Hi, thank you for reporting.
Which hub version do you use? I cannot reproduce this.
I'm using the latest version of hub
- 2.14.2
I do this in three steps.
It's the second and third step that seem to have issues finding the draft release.
@inktomi I still cannot reproduce; I'm able to attach assets to draft releases just fine.
Can you debug by setting HUB_VERBOSE=1 hub release edit ...
and see if anything stands out?
its working
hi thwre
hello
We are running into the same issue, I enabled logging, and here is the result:
I looks like the tag doesn't exist. However, the tag is created upfront and starts the build. The step before this one is the creation of the release from the existing tag. Using actions/create-release@v1
. Which doesn't fail.
Is it possible that this is caused by https://github.com/mislav/hub/issues/2920? The current behavior for finding a specific release is to search through all releases (in pages of 100) to find the one with the matching tag name. I've got a PR up (https://github.com/mislav/hub/pull/3321) to change that to start using the endpoint for actually fetching a single release by tag name, which should alleviate a lot of these types of issue.
คำสั่งพยายาม:
hub release edit v-1.2.3-0 --attach test.png -m ""
เกิดอะไรขึ้น: ไม่พบรุ่นที่มีชื่อแท็ก `v-1.2.3-0'
ข้อมูลเพิ่มเติม:
hub release --include-drafts show v-1.2.3-0
สิ่งนี้แสดงว่ารุ่นนี้เป็นรุ่นที่ไม่ติดแท็ก ฉันสร้างมันผ่านhub release create --draft --message="Test" v-1.2.3-0
Command attempted:
hub release edit v-1.2.3-0 --attach test.png -m ""
What happened: Unable to find release with tag name `v-1.2.3-0'
More info:
hub release --include-drafts show v-1.2.3-0
This shows that the release is an untagged release. I created it viahub release create --draft --message="Test" v-1.2.3-0