-
Notifications
You must be signed in to change notification settings - Fork 756
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
feat: add upload one artifact per file #354
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: initdc <[email protected]>
Hi initdc: |
I am not sure |
Is it possible to upload without .zip with this feat? |
The core logic is repeating the upload process, it still be a zip file. You can upload the original file to release with git hash tag. |
В чём проблема? |
@actions any chance of this being merged? |
@bethanyj28, @konradpabjan, can we get a decision on this please? we really need separate lines for multiple files. this will not affect any existing user as it is brilliantly implemented with a new option |
If you look at the PRs that are getting merged at the moment, it's the kind that are low risk or don't really affect the current action as a product offering. I doubt this will get merged any time soon or even at all, since it would drastically affect githubs bottom line infrastructure wise. |
Any news? |
Since you believe this will never land the main branch, have you considered creating a standalone action? Maybe something called "multiple-upload-artifact"? |
with this feat, we don't need add multi upload-artifact steps
It may has artifact name conflicts in this impl after matrix uploading
It can be improve.
Passed test: https://github.com/initdc/upload-artifact/actions/runs/3273836888
Preview demo: https://github.com/initdc/golang-project-workflow/actions/runs/3255421772
Signed-off-by: initdc [email protected]