mirror of
https://code.forgejo.org/forgejo/download-artifact.git
synced 2025-05-16 12:27:47 +02:00
V2 Updates (#36)
* Update README with compatibilty differences between v1 and v2 * NPM package updates and rebuild index.js * Update README * Compat update
This commit is contained in:
parent
6849460513
commit
d0b19596d3
4 changed files with 165 additions and 79 deletions
25
README.md
25
README.md
|
@ -44,6 +44,31 @@ steps:
|
|||
run: ls -R
|
||||
working-directory: path/to/artifact
|
||||
```
|
||||
|
||||
## Compatibility between `v1` and `v2`
|
||||
|
||||
When using `download-artifact@v1`, a directory denoted by the name of the artifact would be created if the `path` input was not provided. All of the contents would be downloaded to this directory.
|
||||
```
|
||||
current/working/directory/
|
||||
my-artifact/
|
||||
... contents of my-artifact
|
||||
```
|
||||
|
||||
With `v2`, there is no longer an extra directory that is created if the `path` input is not provided. All the contents are downloaded to the current working directory.
|
||||
```
|
||||
current/working/directory/
|
||||
... contents of my-artifact
|
||||
```
|
||||
|
||||
To maintain the same behavior for `v2`, you can set the `path` to the name of the artifact so an extra directory gets created.
|
||||
```
|
||||
- uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: my-artifact
|
||||
path: my-artifact
|
||||
```
|
||||
|
||||
|
||||
# Download All Artifacts
|
||||
|
||||
If the `name` input parameter is not provided, all artifacts will be downloaded. To differentiate between downloaded artifacts, a directory denoted by the artifacts name will be created for each individual artifact.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue