Update README.md
This commit is contained in:
		
							parent
							
								
									f109393e79
								
							
						
					
					
						commit
						58740802ef
					
				| @ -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. | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user