#Upload speed being throttled zip

However, when a workflow run finishes and an artifact is downloaded from either the UI or through the download api, a zip is dynamically created with all the file contents that were uploaded. Limitations Zipped Artifact DownloadsДuring a workflow run, files are uploaded and downloaded individually using the upload-artifact and download-artifact actions. Billing is based on the raw uploaded size and not the size of the zip. When you click to download an artifact from the summary page, a compressed zip is created with all the contents of the artifact and the size of the zip that you download may differ significantly from the displayed size. The displayed artifact size denotes the raw uploaded artifact size (the sum of all the individual files uploaded during the workflow run for the artifact), not the compressed size. The size of the artifact is denoted in bytes. This icon will only appear for users who have write permissions to the repository. There is a trashcan icon that can be used to delete the artifact. Here's a screenshot of something you might see: Where does the upload go?ДЄt the bottom of the workflow summary page, there is a dedicated section for artifacts. For more information see artifact and log retention policies. The retention period must be between 1 and 90 inclusive. Name: my-artifact path: my_file.txt retention-days: 5

name: Create a file run: echo 'I won't live long' > my_file.txt The if-no-files-found option allows you to customize the behavior of the action if no files are found: In certain scenarios it may be desirable to fail the action or suppress the warning.

If a path (or paths), result in no files being found for the artifact, the action will succeed but print out a warning. There is extra documentation around upload limitations and behavior in the toolkit repo that is worth checking out. The package is used internally to handle most of the logic around uploading an artifact. Paths that begin with a wildcard character should be quoted to avoid being interpreted as YAML aliases. Relative paths are rooted against the current working directory. Relative and absolute file paths are both allowed. Exclude paths do not affect the directory structure. If multiple paths are provided as input, the least common ancestor of all the search paths will be used as the root directory of the artifact.

Upload speed being throttled