-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
action: remove old output settings (#146)
* action: remove old output settings Signed-off-by: William Woodruff <[email protected]> * selftest: remove old test ref Signed-off-by: William Woodruff <[email protected]> --------- Signed-off-by: William Woodruff <[email protected]>
- Loading branch information
Showing
4 changed files
with
0 additions
and
130 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -128,81 +128,6 @@ Example: | |
oidc-client-secret: alternative-sigstore-secret | ||
``` | ||
|
||
### `signature` | ||
|
||
**Default**: Empty (signature files will get named as `{input}.sig`) | ||
|
||
The `signature` setting controls the name of the output signature file. This setting does not work | ||
when signing multiple input files. | ||
|
||
Example: | ||
|
||
```yaml | ||
- uses: sigstore/[email protected] | ||
with: | ||
inputs: file.txt | ||
signature: custom-signature-filename.sig | ||
``` | ||
|
||
However, this example is invalid: | ||
|
||
```yaml | ||
- uses: sigstore/[email protected] | ||
with: | ||
inputs: file0.txt file1.txt file2.txt | ||
signature: custom-signature-filename.sig | ||
``` | ||
|
||
### `certificate` | ||
|
||
**Default**: Empty (certificate files will get named as `{input}.crt`) | ||
|
||
The `certificate` setting controls the name of the output certificate file. This setting does not | ||
work when signing multiple input files. | ||
|
||
Example: | ||
|
||
```yaml | ||
- uses: sigstore/[email protected] | ||
with: | ||
inputs: file.txt | ||
certificate: custom-certificate-filename.crt | ||
``` | ||
|
||
However, this example is invalid: | ||
|
||
```yaml | ||
- uses: sigstore/[email protected] | ||
with: | ||
inputs: file0.txt file1.txt file2.txt | ||
certificate: custom-certificate-filename.crt | ||
``` | ||
|
||
### `bundle` | ||
|
||
**Default**: Empty (bundle files will get named as `{input}.sigstore`) | ||
|
||
The `bundle` setting controls the name of the output Sigstore bundle. This setting does not work | ||
when signing multiple input files. | ||
|
||
Example: | ||
|
||
```yaml | ||
- uses: sigstore/[email protected] | ||
with: | ||
inputs: file.txt | ||
bundle: custom-bundle.sigstore | ||
``` | ||
|
||
However, this example is invalid: | ||
|
||
```yaml | ||
- uses: sigstore/[email protected] | ||
with: | ||
inputs: file0.txt file1.txt file2.txt | ||
certificate: custom-bundle.sigstore | ||
``` | ||
|
||
### `staging` | ||
|
||
**Default**: `false` | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters