Open ningyougang opened 3 months ago
Is there any reason for using version 1.8? Have you tried the latest version of this action?
@robinraju ,
Thank you for your reply
Our commany forked this repo using v1.8 version, because for different scenes with same version(v1.8), there has different result, some repos use organization1-repo1-efa4cd0
this style, some repos use organization1-repo1-493ff260f81aeea194227538569ca9935de260fd
style.
So i think it is not version issue.
Maybe somewhere to get the commitId, but i did not find where to get the commitId.
Are you using the extract option provided by the action extract: true
? or manually extracting the file?
Can you copy the workflow step here?
AFAIK, The extract operation doesn't control the directory name. It extracts the contents as it is. Also, we changed the underlying library used for extracting zip files in version 1.10 due to a bug. https://github.com/robinraju/release-downloader/issues/689
I suggest trying the latest version either by updating your forked version or use this action directly.
As an additional step check the process which creates the zip file and verify the zip file contents.
I used release-downloader in our local with this tag: https://github.com/robinraju/release-downloader/commits/v1.8
Let's assume there has two repos
After downloaded, the name of the unzipped folder is different, e.g.
The repo2's folder name just has 7 digits of the whole sha, someone knows the reason?
I hope
organization2/repo2
's unzipped folder isorganization2-repo2-efa4cd07bd0195e6cc65e9e30c251b49ce4d3e51
rather thanorganization2-repo2-efa4cd0