You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attach signing artifacts to GitHub releases if running in a release workflow (#14)
* Expose the signature and certificate outputs as workflow artifacts
* Put each path on a newline
* Cleanup
* Support `--certificate` and `--signature` flags
* Don't write artifact paths if `--no-default-files` has been provided
* Attach signing artifacts to GitHub releases if running in a release workflow
* Fix GH Action name
* Change the trigger from tag pushes to release creation
* action: setting for release artifacts
Signed-off-by: William Woodruff <[email protected]>
* README: document `release-signing-artifacts` setting
Signed-off-by: William Woodruff <[email protected]>
Co-authored-by: William Woodruff <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -298,6 +298,31 @@ Example:
298
298
upload-signing-artifacts: true
299
299
```
300
300
301
+
### `release-signing-artifacts`
302
+
303
+
**Default**: `false`
304
+
305
+
The `release-signing-artifacts` setting controls whether or not `sigstore-python`
306
+
uploads signing artifacts to the release that triggered this run.
307
+
308
+
By default, no release assets are uploaded.
309
+
310
+
Requires the [`contents: write` permission](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token).
0 commit comments