Retain original release info if the keys are not set (#109)
This commit is contained in:
parent
350afcd40d
commit
f6cd293a1e
@ -183,7 +183,12 @@ are not explicitly set and there is already an existing release for the tag, the
|
|||||||
release will retain its original info.
|
release will retain its original info.
|
||||||
=======
|
=======
|
||||||
|
|
||||||
💡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
|
#### outputs
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user