- Assets can be a global regex
- Overwrite assets if wanted
- Reverse (delete all uploaded assets) in case of failure if wanted
- Output with colors and emojis
This action could fail if there are no write permissions on contents.
permissions: contents: write
All default values are passed if the action is used on a
release event workflow, otherwise they missing ones need to be provided since the
event associated might not have all the necessary values.
|always||Paths of the assets to be uploaded, it can be glob regex. It must be a string array. For example: |
|no||GitHub Acess Token. Picked automatically from |
|yes||Tag associated with the release where to upload the assets. Picked automatically from |
|no||Owner of Respository. Picked automatically from |
|no||Repository where to upload assets. Picked automatically from |
|no||Workspace where to search the assets. Picked utomatically from |
|no||Overwrite assets if they’re already in the release.|
|no||Revert (delete all already uploaded assets) in case of failure.|
name: Test Upload Assets To Release on Release Event on: release: types: [published] jobs: test-upload-assets: runs-on: ubuntu-latest permissions: contents: write steps: - uses: actions/checkout@v3 - name: Upload assets to release uses: email@example.com with: files: '["my_asset"]'