Re-order example descriptions (#209)

Given the way that the two descriptions were written it was confusing about which example was being discussed (see specifically "In the above example in the previous version).
This commit is contained in:
Robert Cannon 2021-05-21 13:28:43 -04:00 committed by GitHub
parent 9dc0ee81a2
commit 9243a41f97
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions

View File

@ -125,7 +125,7 @@ If not provided, `artifact` will be used as the default name which will manifest
### Uploading to the same artifact ### Uploading to the same artifact
Each artifact behaves as a file share. Uploading to the same artifact multiple times in the same workflow can overwrite and append already uploaded files With the following example, the available artifact (named `artifact` by default if no name is provided) would contain both `world.txt` (`hello`) and `extra-file.txt` (`howdy`).
```yaml ```yaml
- run: echo hi > world.txt - run: echo hi > world.txt
@ -143,10 +143,11 @@ Each artifact behaves as a file share. Uploading to the same artifact multiple t
with: with:
path: world.txt path: world.txt
``` ```
With the following example, the available artifact (named `artifact` which is the default if no name is provided) would contain both `world.txt` (`hello`) and `extra-file.txt` (`howdy`).
> **_Warning:_** Be careful when uploading to the same artifact via multiple jobs as artifacts may become corrupted > **_Warning:_** Be careful when uploading to the same artifact via multiple jobs as artifacts may become corrupted
Each artifact behaves as a file share. Uploading to the same artifact multiple times in the same workflow can overwrite and append already uploaded files
```yaml ```yaml
strategy: strategy:
matrix: matrix: