chore: 添加内部 artifact 插件镜像
This commit is contained in:
SongJun
22
download/LICENSE
Normal file
22
download/LICENSE
Normal file
@@ -0,0 +1,22 @@
|
|||||||
|
|
||||||
|
The MIT License (MIT)
|
||||||
|
|
||||||
|
Copyright (c) 2018 GitHub, Inc. and contributors
|
||||||
|
|
||||||
|
Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||||
|
of this software and associated documentation files (the "Software"), to deal
|
||||||
|
in the Software without restriction, including without limitation the rights
|
||||||
|
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
||||||
|
copies of the Software, and to permit persons to whom the Software is
|
||||||
|
furnished to do so, subject to the following conditions:
|
||||||
|
|
||||||
|
The above copyright notice and this permission notice shall be included in
|
||||||
|
all copies or substantial portions of the Software.
|
||||||
|
|
||||||
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||||
|
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
||||||
|
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
||||||
|
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||||
|
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||||
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
||||||
|
THE SOFTWARE.
|
||||||
279
download/README.md
Normal file
279
download/README.md
Normal file
@@ -0,0 +1,279 @@
|
|||||||
|
# `@actions/download-artifact`
|
||||||
|
|
||||||
|
Download [Actions Artifacts](https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts) from your Workflow Runs. Internally powered by the [@actions/artifact](https://github.com/actions/toolkit/tree/main/packages/artifact) package.
|
||||||
|
|
||||||
|
See also [upload-artifact](https://github.com/actions/upload-artifact).
|
||||||
|
|
||||||
|
- [`@actions/download-artifact`](#actionsdownload-artifact)
|
||||||
|
- [v4 - What's new](#v4---whats-new)
|
||||||
|
- [Improvements](#improvements)
|
||||||
|
- [Breaking Changes](#breaking-changes)
|
||||||
|
- [Usage](#usage)
|
||||||
|
- [Inputs](#inputs)
|
||||||
|
- [Outputs](#outputs)
|
||||||
|
- [Examples](#examples)
|
||||||
|
- [Download Single Artifact](#download-single-artifact)
|
||||||
|
- [Download Artifacts by ID](#download-artifacts-by-id)
|
||||||
|
- [Download All Artifacts](#download-all-artifacts)
|
||||||
|
- [Download multiple (filtered) Artifacts to the same directory](#download-multiple-filtered-artifacts-to-the-same-directory)
|
||||||
|
- [Download Artifacts from other Workflow Runs or Repositories](#download-artifacts-from-other-workflow-runs-or-repositories)
|
||||||
|
- [Limitations](#limitations)
|
||||||
|
- [Permission Loss](#permission-loss)
|
||||||
|
|
||||||
|
|
||||||
|
## v4 - What's new
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> download-artifact@v4+ is not currently supported on GHES yet. If you are on GHES, you must use [v3](https://github.com/actions/download-artifact/releases/tag/v3).
|
||||||
|
|
||||||
|
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
|
||||||
|
|
||||||
|
For more information, see the [`@actions/artifact`](https://github.com/actions/toolkit/tree/main/packages/artifact) documentation.
|
||||||
|
|
||||||
|
### Improvements
|
||||||
|
|
||||||
|
1. Downloads are significantly faster, upwards of 90% improvement in worst case scenarios.
|
||||||
|
2. Artifacts can be downloaded from other workflow runs and repositories when supplied with a PAT.
|
||||||
|
|
||||||
|
### Breaking Changes
|
||||||
|
|
||||||
|
1. On self hosted runners, additional [firewall rules](https://github.com/actions/toolkit/tree/main/packages/artifact#breaking-changes) may be required.
|
||||||
|
2. Downloading artifacts that were created from `action/upload-artifact@v3` and below are not supported.
|
||||||
|
|
||||||
|
For assistance with breaking changes, see [MIGRATION.md](docs/MIGRATION.md).
|
||||||
|
|
||||||
|
## Usage
|
||||||
|
|
||||||
|
### Inputs
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
# Name of the artifact to download.
|
||||||
|
# If unspecified, all artifacts for the run are downloaded.
|
||||||
|
# Optional.
|
||||||
|
name:
|
||||||
|
|
||||||
|
# IDs of the artifacts to download, comma-separated.
|
||||||
|
# Either inputs `artifact-ids` or `name` can be used, but not both.
|
||||||
|
# Optional.
|
||||||
|
artifact-ids:
|
||||||
|
|
||||||
|
# Destination path. Supports basic tilde expansion.
|
||||||
|
# Optional. Default is $GITHUB_WORKSPACE
|
||||||
|
path:
|
||||||
|
|
||||||
|
# A glob pattern to the artifacts that should be downloaded.
|
||||||
|
# Ignored if name is specified.
|
||||||
|
# Optional.
|
||||||
|
pattern:
|
||||||
|
|
||||||
|
# When multiple artifacts are matched, this changes the behavior of the destination directories.
|
||||||
|
# If true, the downloaded artifacts will be in the same directory specified by path.
|
||||||
|
# If false, the downloaded artifacts will be extracted into individual named directories within the specified path.
|
||||||
|
# Optional. Default is 'false'
|
||||||
|
merge-multiple:
|
||||||
|
|
||||||
|
# The GitHub token used to authenticate with the GitHub API.
|
||||||
|
# This is required when downloading artifacts from a different repository or from a different workflow run.
|
||||||
|
# Optional. If unspecified, the action will download artifacts from the current repo and the current workflow run.
|
||||||
|
github-token:
|
||||||
|
|
||||||
|
# The repository owner and the repository name joined together by "/".
|
||||||
|
# If github-token is specified, this is the repository that artifacts will be downloaded from.
|
||||||
|
# Optional. Default is ${{ github.repository }}
|
||||||
|
repository:
|
||||||
|
|
||||||
|
# The id of the workflow run where the desired download artifact was uploaded from.
|
||||||
|
# If github-token is specified, this is the run that artifacts will be downloaded from.
|
||||||
|
# Optional. Default is ${{ github.run_id }}
|
||||||
|
run-id:
|
||||||
|
```
|
||||||
|
|
||||||
|
### Outputs
|
||||||
|
|
||||||
|
| Name | Description | Example |
|
||||||
|
| - | - | - |
|
||||||
|
| `download-path` | Absolute path where the artifact(s) were downloaded | `/tmp/my/download/path` |
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
### Download Single Artifact
|
||||||
|
|
||||||
|
Download to current working directory (`$GITHUB_WORKSPACE`):
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R
|
||||||
|
```
|
||||||
|
|
||||||
|
Download to a specific directory (also supports `~` expansion):
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: your/destination/dir
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R your/destination/dir
|
||||||
|
```
|
||||||
|
|
||||||
|
### Download Artifacts by ID
|
||||||
|
|
||||||
|
The `artifact-ids` input allows downloading artifacts using their unique ID rather than name. This is particularly useful when working with immutable artifacts from `actions/upload-artifact@v4` which assigns a unique ID to each artifact.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
artifact-ids: 12345
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R
|
||||||
|
```
|
||||||
|
|
||||||
|
Multiple artifacts can be downloaded by providing a comma-separated list of IDs:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
artifact-ids: 12345,67890
|
||||||
|
path: path/to/artifacts
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R path/to/artifacts
|
||||||
|
```
|
||||||
|
|
||||||
|
This will download multiple artifacts to separate directories (similar to downloading multiple artifacts by name).
|
||||||
|
|
||||||
|
### Download All Artifacts
|
||||||
|
|
||||||
|
If the `name` input parameter is not provided, all artifacts will be downloaded. To differentiate between downloaded artifacts, by default a directory denoted by the artifacts name will be created for each individual artifact. This behavior can be changed with the `merge-multiple` input parameter.
|
||||||
|
|
||||||
|
Example, if there are two artifacts `Artifact-A` and `Artifact-B`, and the directory is `etc/usr/artifacts/`, the directory structure will look like this:
|
||||||
|
|
||||||
|
```
|
||||||
|
etc/usr/artifacts/
|
||||||
|
Artifact-A/
|
||||||
|
... contents of Artifact-A
|
||||||
|
Artifact-B/
|
||||||
|
... contents of Artifact-B
|
||||||
|
```
|
||||||
|
|
||||||
|
Download all artifacts to the current working directory:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R
|
||||||
|
```
|
||||||
|
|
||||||
|
Download all artifacts to a specific directory:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
path: path/to/artifacts
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R path/to/artifacts
|
||||||
|
```
|
||||||
|
|
||||||
|
To download them to the _same_ directory:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
path: path/to/artifacts
|
||||||
|
merge-multiple: true
|
||||||
|
- name: Display structure of downloaded files
|
||||||
|
run: ls -R path/to/artifacts
|
||||||
|
```
|
||||||
|
|
||||||
|
Which will result in:
|
||||||
|
|
||||||
|
```
|
||||||
|
path/to/artifacts/
|
||||||
|
... contents of Artifact-A
|
||||||
|
... contents of Artifact-B
|
||||||
|
```
|
||||||
|
|
||||||
|
### Download multiple (filtered) Artifacts to the same directory
|
||||||
|
|
||||||
|
In multiple arch/os scenarios, you may have Artifacts built in different jobs. To download all Artifacts to the same directory (or matching a glob pattern), you can use the `pattern` and `merge-multiple` inputs.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
jobs:
|
||||||
|
upload:
|
||||||
|
strategy:
|
||||||
|
matrix:
|
||||||
|
runs-on: [ubuntu-latest, macos-latest, windows-latest]
|
||||||
|
runs-on: ${{ matrix.runs-on }}
|
||||||
|
steps:
|
||||||
|
- name: Create a File
|
||||||
|
run: echo "hello from ${{ matrix.runs-on }}" > file-${{ matrix.runs-on }}.txt
|
||||||
|
- name: Upload Artifact
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact-${{ matrix.runs-on }}
|
||||||
|
path: file-${{ matrix.runs-on }}.txt
|
||||||
|
download:
|
||||||
|
needs: upload
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
steps:
|
||||||
|
- name: Download All Artifacts
|
||||||
|
uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
path: my-artifact
|
||||||
|
pattern: my-artifact-*
|
||||||
|
merge-multiple: true
|
||||||
|
- run: ls -R my-artifact
|
||||||
|
```
|
||||||
|
|
||||||
|
This results in a directory like so:
|
||||||
|
|
||||||
|
```
|
||||||
|
my-artifact/
|
||||||
|
file-macos-latest.txt
|
||||||
|
file-ubuntu-latest.txt
|
||||||
|
file-windows-latest.txt
|
||||||
|
```
|
||||||
|
|
||||||
|
### Download Artifacts from other Workflow Runs or Repositories
|
||||||
|
|
||||||
|
It may be useful to download Artifacts from other workflow runs, or even other repositories. By default, the permissions are scoped so they can only download Artifacts within the current workflow run. To elevate permissions for this scenario, you can specify a `github-token` along with other repository and run identifiers:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- uses: actions/download-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-other-artifact
|
||||||
|
github-token: ${{ secrets.GH_PAT }} # token with actions:read permissions on target repo
|
||||||
|
repository: actions/toolkit
|
||||||
|
run-id: 1234
|
||||||
|
```
|
||||||
|
|
||||||
|
## Limitations
|
||||||
|
|
||||||
|
### Permission Loss
|
||||||
|
|
||||||
|
File permissions are not maintained during artifact upload. All directories will have `755` and all files will have `644`. 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.
|
||||||
|
|
||||||
|
If you must preserve permissions, you can `tar` all of your files together before artifact upload. Post download, the `tar` file will maintain file permissions and case sensitivity.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- name: 'Tar files'
|
||||||
|
run: tar -cvf my_files.tar /path/to/my/directory
|
||||||
|
|
||||||
|
- name: 'Upload Artifact'
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: my_files.tar
|
||||||
|
```
|
||||||
43
download/action.yml
Normal file
43
download/action.yml
Normal file
@@ -0,0 +1,43 @@
|
|||||||
|
name: 'Download a Build Artifact'
|
||||||
|
description: 'Download a build artifact that was previously uploaded in the workflow by the upload-artifact action'
|
||||||
|
author: 'GitHub'
|
||||||
|
inputs:
|
||||||
|
name:
|
||||||
|
description: 'Name of the artifact to download. If unspecified, all artifacts for the run are downloaded.'
|
||||||
|
required: false
|
||||||
|
artifact-ids:
|
||||||
|
description: 'IDs of the artifacts to download, comma-separated. Either inputs `artifact-ids` or `name` can be used, but not both.'
|
||||||
|
required: false
|
||||||
|
path:
|
||||||
|
description: 'Destination path. Supports basic tilde expansion. Defaults to $GITHUB_WORKSPACE'
|
||||||
|
required: false
|
||||||
|
pattern:
|
||||||
|
description: 'A glob pattern matching the artifacts that should be downloaded. Ignored if name is specified.'
|
||||||
|
required: false
|
||||||
|
merge-multiple:
|
||||||
|
description: 'When multiple artifacts are matched, this changes the behavior of the destination directories.
|
||||||
|
If true, the downloaded artifacts will be in the same directory specified by path.
|
||||||
|
If false, the downloaded artifacts will be extracted into individual named directories within the specified path.'
|
||||||
|
required: false
|
||||||
|
default: 'false'
|
||||||
|
github-token:
|
||||||
|
description: 'The GitHub token used to authenticate with the GitHub API.
|
||||||
|
This is required when downloading artifacts from a different repository or from a different workflow run.
|
||||||
|
If this is not specified, the action will attempt to download artifacts from the current repository and the current workflow run.'
|
||||||
|
required: false
|
||||||
|
repository:
|
||||||
|
description: 'The repository owner and the repository name joined together by "/".
|
||||||
|
If github-token is specified, this is the repository that artifacts will be downloaded from.'
|
||||||
|
required: false
|
||||||
|
default: ${{ github.repository }}
|
||||||
|
run-id:
|
||||||
|
description: 'The id of the workflow run where the desired download artifact was uploaded from.
|
||||||
|
If github-token is specified, this is the run that artifacts will be downloaded from.'
|
||||||
|
required: false
|
||||||
|
default: ${{ github.run_id }}
|
||||||
|
outputs:
|
||||||
|
download-path:
|
||||||
|
description: 'Path of artifact download'
|
||||||
|
runs:
|
||||||
|
using: 'node20'
|
||||||
|
main: 'dist/index.js'
|
||||||
128961
download/dist/index.js
vendored
Normal file
128961
download/dist/index.js
vendored
Normal file
File diff suppressed because one or more lines are too long
22
upload/LICENSE
Normal file
22
upload/LICENSE
Normal file
@@ -0,0 +1,22 @@
|
|||||||
|
|
||||||
|
The MIT License (MIT)
|
||||||
|
|
||||||
|
Copyright (c) 2018 GitHub, Inc. and contributors
|
||||||
|
|
||||||
|
Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||||
|
of this software and associated documentation files (the "Software"), to deal
|
||||||
|
in the Software without restriction, including without limitation the rights
|
||||||
|
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
||||||
|
copies of the Software, and to permit persons to whom the Software is
|
||||||
|
furnished to do so, subject to the following conditions:
|
||||||
|
|
||||||
|
The above copyright notice and this permission notice shall be included in
|
||||||
|
all copies or substantial portions of the Software.
|
||||||
|
|
||||||
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||||
|
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
||||||
|
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
||||||
|
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||||
|
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||||
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
||||||
|
THE SOFTWARE.
|
||||||
480
upload/README.md
Normal file
480
upload/README.md
Normal file
@@ -0,0 +1,480 @@
|
|||||||
|
# `@actions/upload-artifact`
|
||||||
|
|
||||||
|
> [!WARNING]
|
||||||
|
> actions/upload-artifact@v3 is scheduled for deprecation on **November 30, 2024**. [Learn more.](https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/)
|
||||||
|
> Similarly, v1/v2 are scheduled for deprecation on **June 30, 2024**.
|
||||||
|
> Please update your workflow to use v4 of the artifact actions.
|
||||||
|
> This deprecation will not impact any existing versions of GitHub Enterprise Server being used by customers.
|
||||||
|
|
||||||
|
Upload [Actions Artifacts](https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts) from your Workflow Runs. Internally powered by [@actions/artifact](https://github.com/actions/toolkit/tree/main/packages/artifact) package.
|
||||||
|
|
||||||
|
See also [download-artifact](https://github.com/actions/download-artifact).
|
||||||
|
|
||||||
|
- [`@actions/upload-artifact`](#actionsupload-artifact)
|
||||||
|
- [v4 - What's new](#v4---whats-new)
|
||||||
|
- [Improvements](#improvements)
|
||||||
|
- [Breaking Changes](#breaking-changes)
|
||||||
|
- [Usage](#usage)
|
||||||
|
- [Inputs](#inputs)
|
||||||
|
- [Outputs](#outputs)
|
||||||
|
- [Examples](#examples)
|
||||||
|
- [Upload an Individual File](#upload-an-individual-file)
|
||||||
|
- [Upload an Entire Directory](#upload-an-entire-directory)
|
||||||
|
- [Upload using a Wildcard Pattern](#upload-using-a-wildcard-pattern)
|
||||||
|
- [Upload using Multiple Paths and Exclusions](#upload-using-multiple-paths-and-exclusions)
|
||||||
|
- [Altering compressions level (speed v. size)](#altering-compressions-level-speed-v-size)
|
||||||
|
- [Customization if no files are found](#customization-if-no-files-are-found)
|
||||||
|
- [(Not) Uploading to the same artifact](#not-uploading-to-the-same-artifact)
|
||||||
|
- [Environment Variables and Tilde Expansion](#environment-variables-and-tilde-expansion)
|
||||||
|
- [Retention Period](#retention-period)
|
||||||
|
- [Using Outputs](#using-outputs)
|
||||||
|
- [Example output between steps](#example-output-between-steps)
|
||||||
|
- [Example output between jobs](#example-output-between-jobs)
|
||||||
|
- [Overwriting an Artifact](#overwriting-an-artifact)
|
||||||
|
- [Limitations](#limitations)
|
||||||
|
- [Number of Artifacts](#number-of-artifacts)
|
||||||
|
- [Zip archives](#zip-archives)
|
||||||
|
- [Permission Loss](#permission-loss)
|
||||||
|
- [Where does the upload go?](#where-does-the-upload-go)
|
||||||
|
|
||||||
|
|
||||||
|
## v4 - What's new
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> upload-artifact@v4+ is not currently supported on GHES yet. If you are on GHES, you must use [v3](https://github.com/actions/upload-artifact/releases/tag/v3).
|
||||||
|
|
||||||
|
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
|
||||||
|
|
||||||
|
For more information, see the [`@actions/artifact`](https://github.com/actions/toolkit/tree/main/packages/artifact) documentation.
|
||||||
|
|
||||||
|
There is also a new sub-action, `actions/upload-artifact/merge`. For more info, check out that action's [README](./merge/README.md).
|
||||||
|
|
||||||
|
### Improvements
|
||||||
|
|
||||||
|
1. Uploads are significantly faster, upwards of 90% improvement in worst case scenarios.
|
||||||
|
2. Once uploaded, an Artifact ID is returned and Artifacts are immediately available in the UI and [REST API](https://docs.github.com/en/rest/actions/artifacts). Previously, you would have to wait for the run to be completed before an ID was available or any APIs could be utilized.
|
||||||
|
3. The contents of an Artifact are uploaded together into an _immutable_ archive. They cannot be altered by subsequent jobs unless the Artifacts are deleted and recreated (where they will have a new ID). Both of these factors help reduce the possibility of accidentally corrupting Artifact files.
|
||||||
|
4. The compression level of an Artifact can be manually tweaked for speed or size reduction.
|
||||||
|
|
||||||
|
### Breaking Changes
|
||||||
|
|
||||||
|
1. On self hosted runners, additional [firewall rules](https://github.com/actions/toolkit/tree/main/packages/artifact#breaking-changes) may be required.
|
||||||
|
2. Uploading to the same named Artifact multiple times.
|
||||||
|
|
||||||
|
Due to how Artifacts are created in this new version, it is no longer possible to upload to the same named Artifact multiple times. You must either split the uploads into multiple Artifacts with different names, or only upload once. Otherwise you _will_ encounter an error.
|
||||||
|
|
||||||
|
3. Limit of Artifacts for an individual job. Each job in a workflow run now has a limit of 500 artifacts.
|
||||||
|
4. With `v4.4` and later, hidden files are excluded by default.
|
||||||
|
|
||||||
|
For assistance with breaking changes, see [MIGRATION.md](docs/MIGRATION.md).
|
||||||
|
|
||||||
|
## Usage
|
||||||
|
|
||||||
|
### Inputs
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
# Name of the artifact to upload.
|
||||||
|
# Optional. Default is 'artifact'
|
||||||
|
name:
|
||||||
|
|
||||||
|
# A file, directory or wildcard pattern that describes what to upload
|
||||||
|
# Required.
|
||||||
|
path:
|
||||||
|
|
||||||
|
# The desired behavior if no files are found using the provided path.
|
||||||
|
# Available Options:
|
||||||
|
# warn: Output a warning but do not fail the action
|
||||||
|
# error: Fail the action with an error message
|
||||||
|
# ignore: Do not output any warnings or errors, the action does not fail
|
||||||
|
# Optional. Default is 'warn'
|
||||||
|
if-no-files-found:
|
||||||
|
|
||||||
|
# Duration after which artifact will expire in days. 0 means using default retention.
|
||||||
|
# Minimum 1 day.
|
||||||
|
# Maximum 90 days unless changed from the repository settings page.
|
||||||
|
# Optional. Defaults to repository settings.
|
||||||
|
retention-days:
|
||||||
|
|
||||||
|
# The level of compression for Zlib to be applied to the artifact archive.
|
||||||
|
# The value can range from 0 to 9.
|
||||||
|
# For large files that are not easily compressed, a value of 0 is recommended for significantly faster uploads.
|
||||||
|
# Optional. Default is '6'
|
||||||
|
compression-level:
|
||||||
|
|
||||||
|
# If true, an artifact with a matching name will be deleted before a new one is uploaded.
|
||||||
|
# If false, the action will fail if an artifact for the given name already exists.
|
||||||
|
# Does not fail if the artifact does not exist.
|
||||||
|
# Optional. Default is 'false'
|
||||||
|
overwrite:
|
||||||
|
|
||||||
|
# Whether to include hidden files in the provided path in the artifact
|
||||||
|
# The file contents of any hidden files in the path should be validated before
|
||||||
|
# enabled this to avoid uploading sensitive information.
|
||||||
|
# Optional. Default is 'false'
|
||||||
|
include-hidden-files:
|
||||||
|
```
|
||||||
|
|
||||||
|
### Outputs
|
||||||
|
|
||||||
|
| Name | Description | Example |
|
||||||
|
| - | - | - |
|
||||||
|
| `artifact-id` | GitHub ID of an Artifact, can be used by the REST API | `1234` |
|
||||||
|
| `artifact-url` | URL to download an Artifact. Can be used in many scenarios such as linking to artifacts in issues or pull requests. Users must be logged-in in order for this URL to work. This URL is valid as long as the artifact has not expired or the artifact, run or repository have not been deleted | `https://github.com/example-org/example-repo/actions/runs/1/artifacts/1234` |
|
||||||
|
| `artifact-digest` | SHA-256 digest of an Artifact | 0fde654d4c6e659b45783a725dc92f1bfb0baa6c2de64b34e814dc206ff4aaaf |
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
### Upload an Individual File
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- run: mkdir -p path/to/artifact
|
||||||
|
- run: echo hello > path/to/artifact/world.txt
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: path/to/artifact/world.txt
|
||||||
|
```
|
||||||
|
|
||||||
|
### Upload an Entire Directory
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: path/to/artifact/ # or path/to/artifact
|
||||||
|
```
|
||||||
|
|
||||||
|
### Upload using a Wildcard Pattern
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: path/**/[abc]rtifac?/*
|
||||||
|
```
|
||||||
|
|
||||||
|
### Upload using Multiple Paths and Exclusions
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: |
|
||||||
|
path/output/bin/
|
||||||
|
path/output/test-results
|
||||||
|
!path/**/*.tmp
|
||||||
|
```
|
||||||
|
|
||||||
|
For supported wildcards along with behavior and documentation, see [@actions/glob](https://github.com/actions/toolkit/tree/main/packages/glob) which is used internally to search for files.
|
||||||
|
|
||||||
|
If a wildcard pattern is used, the path hierarchy will be preserved after the first wildcard pattern:
|
||||||
|
|
||||||
|
```
|
||||||
|
path/to/*/directory/foo?.txt =>
|
||||||
|
∟ path/to/some/directory/foo1.txt
|
||||||
|
∟ path/to/some/directory/foo2.txt
|
||||||
|
∟ path/to/other/directory/foo1.txt
|
||||||
|
|
||||||
|
would be flattened and uploaded as =>
|
||||||
|
∟ some/directory/foo1.txt
|
||||||
|
∟ some/directory/foo2.txt
|
||||||
|
∟ other/directory/foo1.txt
|
||||||
|
```
|
||||||
|
|
||||||
|
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. Exclude paths do not affect the directory structure.
|
||||||
|
|
||||||
|
Relative and absolute file paths are both allowed. Relative paths are rooted against the current working directory. Paths that begin with a wildcard character should be quoted to avoid being interpreted as YAML aliases.
|
||||||
|
|
||||||
|
### Altering compressions level (speed v. size)
|
||||||
|
|
||||||
|
If you are uploading large or easily compressable data to your artifact, you may benefit from tweaking the compression level. By default, the compression level is `6`, the same as GNU Gzip.
|
||||||
|
|
||||||
|
The value can range from 0 to 9:
|
||||||
|
- 0: No compression
|
||||||
|
- 1: Best speed
|
||||||
|
- 6: Default compression (same as GNU Gzip)
|
||||||
|
- 9: Best compression
|
||||||
|
|
||||||
|
Higher levels will result in better compression, but will take longer to complete.
|
||||||
|
For large files that are not easily compressed, a value of `0` is recommended for significantly faster uploads.
|
||||||
|
|
||||||
|
For instance, if you are uploading random binary data, you can save a lot of time by opting out of compression completely, since it won't benefit:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- name: Make a 1GB random binary file
|
||||||
|
run: |
|
||||||
|
dd if=/dev/urandom of=my-1gb-file bs=1M count=1000
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: my-1gb-file
|
||||||
|
compression-level: 0 # no compression
|
||||||
|
```
|
||||||
|
|
||||||
|
But, if you are uploading data that is easily compressed (like plaintext, code, etc) you can save space and cost by having a higher compression level. But this will be heavier on the CPU therefore slower to upload:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- name: Make a file with a lot of repeated text
|
||||||
|
run: |
|
||||||
|
for i in {1..100000}; do echo -n 'foobar' >> foobar.txt; done
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: foobar.txt
|
||||||
|
compression-level: 9 # maximum compression
|
||||||
|
```
|
||||||
|
|
||||||
|
### Customization if no files are found
|
||||||
|
|
||||||
|
If a path (or paths), result in no files being found for the artifact, the action will succeed but print out a warning. In certain scenarios it may be desirable to fail the action or suppress the warning. The `if-no-files-found` option allows you to customize the behavior of the action if no files are found:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: path/to/artifact/
|
||||||
|
if-no-files-found: error # 'warn' or 'ignore' are also available, defaults to `warn`
|
||||||
|
```
|
||||||
|
|
||||||
|
### (Not) Uploading to the same artifact
|
||||||
|
|
||||||
|
Unlike earlier versions of `upload-artifact`, uploading to the same artifact via multiple jobs is _not_ supported with `v4`.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- run: echo hi > world.txt
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
# implicitly named as 'artifact'
|
||||||
|
path: world.txt
|
||||||
|
|
||||||
|
- run: echo howdy > extra-file.txt
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
# also implicitly named as 'artifact', will fail here!
|
||||||
|
path: extra-file.txt
|
||||||
|
```
|
||||||
|
|
||||||
|
Artifact names must be unique since each created artifact is idempotent so multiple jobs cannot modify the same artifact.
|
||||||
|
|
||||||
|
In matrix scenarios, be careful to not accidentally upload to the same artifact, or else you will encounter conflict errors. It would be best to name the artifact _with_ a prefix or suffix from the matrix:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
jobs:
|
||||||
|
upload:
|
||||||
|
name: Generate Build Artifacts
|
||||||
|
|
||||||
|
strategy:
|
||||||
|
matrix:
|
||||||
|
os: [ubuntu-latest, windows-latest]
|
||||||
|
version: [a, b, c]
|
||||||
|
|
||||||
|
runs-on: ${{ matrix.os }}
|
||||||
|
|
||||||
|
steps:
|
||||||
|
- name: Build
|
||||||
|
run: ./some-script --version=${{ matrix.version }} > my-binary
|
||||||
|
- name: Upload
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: binary-${{ matrix.os }}-${{ matrix.version }}
|
||||||
|
path: my-binary
|
||||||
|
```
|
||||||
|
|
||||||
|
This will result in artifacts like: `binary-ubuntu-latest-a`, `binary-windows-latest-b`, and so on.
|
||||||
|
|
||||||
|
Previously the behavior _allowed_ for the artifact names to be the same which resulted in unexpected mutations and accidental corruption. Artifacts created by upload-artifact@v4 are immutable.
|
||||||
|
|
||||||
|
### Environment Variables and Tilde Expansion
|
||||||
|
|
||||||
|
You can use `~` in the path input as a substitute for `$HOME`. Basic tilde expansion is supported:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- run: |
|
||||||
|
mkdir -p ~/new/artifact
|
||||||
|
echo hello > ~/new/artifact/world.txt
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifacts
|
||||||
|
path: ~/new/**/*
|
||||||
|
```
|
||||||
|
|
||||||
|
Environment variables along with context expressions can also be used for input. For documentation see [context and expression syntax](https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions):
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
env:
|
||||||
|
name: my-artifact
|
||||||
|
steps:
|
||||||
|
- run: |
|
||||||
|
mkdir -p ${{ github.workspace }}/artifact
|
||||||
|
echo hello > ${{ github.workspace }}/artifact/world.txt
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: ${{ env.name }}-name
|
||||||
|
path: ${{ github.workspace }}/artifact/**/*
|
||||||
|
```
|
||||||
|
|
||||||
|
For environment variables created in other steps, make sure to use the `env` expression syntax
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
- run: |
|
||||||
|
mkdir testing
|
||||||
|
echo "This is a file to upload" > testing/file.txt
|
||||||
|
echo "artifactPath=testing/file.txt" >> $GITHUB_ENV
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: artifact
|
||||||
|
path: ${{ env.artifactPath }} # this will resolve to testing/file.txt at runtime
|
||||||
|
```
|
||||||
|
|
||||||
|
### Retention Period
|
||||||
|
|
||||||
|
Artifacts are retained for 90 days by default. You can specify a shorter retention period using the `retention-days` input:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- name: Create a file
|
||||||
|
run: echo "I won't live long" > my_file.txt
|
||||||
|
|
||||||
|
- name: Upload Artifact
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: my_file.txt
|
||||||
|
retention-days: 5
|
||||||
|
```
|
||||||
|
|
||||||
|
The retention period must be between 1 and 90 inclusive. For more information see [artifact and log retention policies](https://docs.github.com/en/free-pro-team@latest/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy).
|
||||||
|
|
||||||
|
### Using Outputs
|
||||||
|
|
||||||
|
If an artifact upload is successful then an `artifact-id` output is available. This ID is a unique identifier that can be used with [Artifact REST APIs](https://docs.github.com/en/rest/actions/artifacts).
|
||||||
|
|
||||||
|
#### Example output between steps
|
||||||
|
|
||||||
|
```yml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
id: artifact-upload-step
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: path/to/artifact/content/
|
||||||
|
|
||||||
|
- name: Output artifact ID
|
||||||
|
run: echo 'Artifact ID is ${{ steps.artifact-upload-step.outputs.artifact-id }}'
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Example output between jobs
|
||||||
|
|
||||||
|
```yml
|
||||||
|
jobs:
|
||||||
|
job1:
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
outputs:
|
||||||
|
output1: ${{ steps.artifact-upload-step.outputs.artifact-id }}
|
||||||
|
steps:
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
id: artifact-upload-step
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: path/to/artifact/content/
|
||||||
|
job2:
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
needs: job1
|
||||||
|
steps:
|
||||||
|
- env:
|
||||||
|
OUTPUT1: ${{needs.job1.outputs.output1}}
|
||||||
|
run: echo "Artifact ID from previous job is $OUTPUT1"
|
||||||
|
```
|
||||||
|
|
||||||
|
### Overwriting an Artifact
|
||||||
|
|
||||||
|
Although it's not possible to mutate an Artifact, can completely overwrite one. But do note that this will give the Artifact a new ID, the previous one will no longer exist:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
jobs:
|
||||||
|
upload:
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
steps:
|
||||||
|
- name: Create a file
|
||||||
|
run: echo "hello world" > my-file.txt
|
||||||
|
- name: Upload Artifact
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact # NOTE: same artifact name
|
||||||
|
path: my-file.txt
|
||||||
|
upload-again:
|
||||||
|
needs: upload
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
steps:
|
||||||
|
- name: Create a different file
|
||||||
|
run: echo "goodbye world" > my-file.txt
|
||||||
|
- name: Upload Artifact
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact # NOTE: same artifact name
|
||||||
|
path: my-file.txt
|
||||||
|
overwrite: true
|
||||||
|
```
|
||||||
|
|
||||||
|
### Uploading Hidden Files
|
||||||
|
|
||||||
|
By default, hidden files are ignored by this action to avoid unintentionally uploading sensitive information.
|
||||||
|
|
||||||
|
If you need to upload hidden files, you can use the `include-hidden-files` input.
|
||||||
|
Any files that contain sensitive information that should not be in the uploaded artifact can be excluded
|
||||||
|
using the `path`:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
include-hidden-files: true
|
||||||
|
path: |
|
||||||
|
path/output/
|
||||||
|
!path/output/.production.env
|
||||||
|
```
|
||||||
|
|
||||||
|
Hidden files are defined as any file beginning with `.` or files within folders beginning with `.`.
|
||||||
|
On Windows, files and directories with the hidden attribute are not considered hidden files unless
|
||||||
|
they have the `.` prefix.
|
||||||
|
|
||||||
|
## Limitations
|
||||||
|
|
||||||
|
### Number of Artifacts
|
||||||
|
|
||||||
|
Within an individual job, there is a limit of 500 artifacts that can be created for that job.
|
||||||
|
|
||||||
|
You may also be limited by Artifacts if you have exceeded your shared storage quota. Storage is calculated every 6-12 hours. See [the documentation](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions#calculating-minute-and-storage-spending) for more info.
|
||||||
|
|
||||||
|
### Zip archives
|
||||||
|
|
||||||
|
When an Artifact is uploaded, all the files are assembled into an immutable Zip archive. There is currently no way to download artifacts in a format other than a Zip or to download individual artifact contents.
|
||||||
|
|
||||||
|
### Permission Loss
|
||||||
|
|
||||||
|
File permissions are not maintained during artifact upload. All directories will have `755` and all files will have `644`. 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.
|
||||||
|
|
||||||
|
If you must preserve permissions, you can `tar` all of your files together before artifact upload. Post download, the `tar` file will maintain file permissions and case sensitivity.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
- name: 'Tar files'
|
||||||
|
run: tar -cvf my_files.tar /path/to/my/directory
|
||||||
|
|
||||||
|
- name: 'Upload Artifact'
|
||||||
|
uses: actions/upload-artifact@v4
|
||||||
|
with:
|
||||||
|
name: my-artifact
|
||||||
|
path: my_files.tar
|
||||||
|
```
|
||||||
|
|
||||||
|
## Where does the upload go?
|
||||||
|
|
||||||
|
At the bottom of the workflow summary page, there is a dedicated section for artifacts. Here's a screenshot of something you might see:
|
||||||
|
|
||||||
|
<img src="https://user-images.githubusercontent.com/16109154/103645952-223c6880-4f59-11eb-8268-8dca6937b5f9.png" width="700" height="300">
|
||||||
|
|
||||||
|
There is a trashcan icon that can be used to delete the artifact. This icon will only appear for users who have write permissions to the repository.
|
||||||
|
|
||||||
|
The size of the artifact is denoted in bytes. The displayed artifact size denotes the size of the zip that `upload-artifact` creates during upload.
|
||||||
69
upload/action.yml
Normal file
69
upload/action.yml
Normal file
@@ -0,0 +1,69 @@
|
|||||||
|
name: 'Upload a Build Artifact'
|
||||||
|
description: 'Upload a build artifact that can be used by subsequent workflow steps'
|
||||||
|
author: 'GitHub'
|
||||||
|
inputs:
|
||||||
|
name:
|
||||||
|
description: 'Artifact name'
|
||||||
|
default: 'artifact'
|
||||||
|
path:
|
||||||
|
description: 'A file, directory or wildcard pattern that describes what to upload'
|
||||||
|
required: true
|
||||||
|
if-no-files-found:
|
||||||
|
description: >
|
||||||
|
The desired behavior if no files are found using the provided path.
|
||||||
|
|
||||||
|
Available Options:
|
||||||
|
warn: Output a warning but do not fail the action
|
||||||
|
error: Fail the action with an error message
|
||||||
|
ignore: Do not output any warnings or errors, the action does not fail
|
||||||
|
default: 'warn'
|
||||||
|
retention-days:
|
||||||
|
description: >
|
||||||
|
Duration after which artifact will expire in days. 0 means using default retention.
|
||||||
|
|
||||||
|
Minimum 1 day.
|
||||||
|
Maximum 90 days unless changed from the repository settings page.
|
||||||
|
compression-level:
|
||||||
|
description: >
|
||||||
|
The level of compression for Zlib to be applied to the artifact archive.
|
||||||
|
The value can range from 0 to 9:
|
||||||
|
- 0: No compression
|
||||||
|
- 1: Best speed
|
||||||
|
- 6: Default compression (same as GNU Gzip)
|
||||||
|
- 9: Best compression
|
||||||
|
Higher levels will result in better compression, but will take longer to complete.
|
||||||
|
For large files that are not easily compressed, a value of 0 is recommended for significantly faster uploads.
|
||||||
|
default: '6'
|
||||||
|
overwrite:
|
||||||
|
description: >
|
||||||
|
If true, an artifact with a matching name will be deleted before a new one is uploaded.
|
||||||
|
If false, the action will fail if an artifact for the given name already exists.
|
||||||
|
Does not fail if the artifact does not exist.
|
||||||
|
default: 'false'
|
||||||
|
include-hidden-files:
|
||||||
|
description: >
|
||||||
|
If true, hidden files will be included in the artifact.
|
||||||
|
If false, hidden files will be excluded from the artifact.
|
||||||
|
default: 'false'
|
||||||
|
|
||||||
|
outputs:
|
||||||
|
artifact-id:
|
||||||
|
description: >
|
||||||
|
A unique identifier for the artifact that was just uploaded. Empty if the artifact upload failed.
|
||||||
|
|
||||||
|
This ID can be used as input to other APIs to download, delete or get more information about an artifact: https://docs.github.com/en/rest/actions/artifacts
|
||||||
|
artifact-url:
|
||||||
|
description: >
|
||||||
|
A download URL for the artifact that was just uploaded. Empty if the artifact upload failed.
|
||||||
|
|
||||||
|
This download URL only works for requests Authenticated with GitHub. Anonymous downloads will be prompted to first login.
|
||||||
|
If an anonymous download URL is needed than a short time restricted URL can be generated using the download artifact API: https://docs.github.com/en/rest/actions/artifacts#download-an-artifact
|
||||||
|
|
||||||
|
This URL will be valid for as long as the artifact exists and the workflow run and repository exists. Once an artifact has expired this URL will no longer work.
|
||||||
|
Common uses cases for such a download URL can be adding download links to artifacts in descriptions or comments on pull requests or issues.
|
||||||
|
artifact-digest:
|
||||||
|
description: >
|
||||||
|
SHA-256 digest for the artifact that was just uploaded. Empty if the artifact upload failed.
|
||||||
|
runs:
|
||||||
|
using: 'node20'
|
||||||
|
main: 'dist/upload/index.js'
|
||||||
135926
upload/dist/index.js
vendored
Normal file
135926
upload/dist/index.js
vendored
Normal file
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user