actions/upload-artifact
1
Fork 0
mirror of https://gitea.com/actions/upload-artifact.git synced 2024-11-23 00:55:58 +01:00
Code Activity

Update README.md

Browse source
This commit is contained in:
Konrad Pabjan 2020-08-11 18:20:19 +02:00 committed by GitHub
parent f109393e79
commit 58740802ef
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -207,6 +207,10 @@ There is a trashcan icon that can be used to delete the artifact. This icon will
# Limitations # Limitations
### Zipped Artifact Downloads
During a workflow run, files are uploaded and downloaded indivdually using the `upload-artifact` and `download-artifact` actions. However, when a workflow run finishes and an artifact is downloaded from either the UI or through the [download api](https://developer.github.com/v3/actions/artifacts/#download-an-artifact), a zip is dynamically created with all the file contents that were uploaded. There is currently no way to download artifacts after a workflow run finishes in a format other than a zip or to download artifact contents individually. One of the consequences of this limitation is that if a zip is uploaded during a workflow run and then downloaded from the UI, there will be a double zip created.
### Permission Loss ### Permission Loss
:exclamation: File permissions are not maintained during artifact upload :exclamation: For example, if you make a file executable using `chmod` and then upload that file, post-download the file is no longer guaranteed to be set as an executable. :exclamation: File permissions are not maintained during artifact upload :exclamation: For example, if you make a file executable using `chmod` and then upload that file, post-download the file is no longer guaranteed to be set as an executable.