Retain original release info if the keys are not set (#109)

This commit is contained in:
Filip Š 2021-07-18 01:27:42 +02:00 committed by softprops
parent ec9df7c385
commit 75dbd0cd0e
5 changed files with 57 additions and 12 deletions

View file

@ -185,7 +185,12 @@ The following are optional as `step.with` keys
| `fail_on_unmatched_files` | Boolean | Indicator of whether to fail if any of the `files` globs match nothing |
| `target_commitish` | String | Commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. |
💡When providing a `body` and `body_path` at the same time, `body_path` will be attempted first, then falling back on `body` if the path can not be read from.
💡 When providing a `body` and `body_path` at the same time, `body_path` will be
attempted first, then falling back on `body` if the path can not be read from.
💡 When the release info keys (such as `name`, `body`, `draft`, `prerelease`, etc.)
are not explicitly set and there is already an existing release for the tag, the
release will retain its original info.
#### outputs