From bcb48d22ce28521a082f4164b4ce17808888cd9c Mon Sep 17 00:00:00 2001 From: Sam Seay Date: Fri, 13 Jan 2023 11:26:58 +1300 Subject: [PATCH] Update input documentation. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0175b06..497f720 100644 --- a/README.md +++ b/README.md @@ -181,7 +181,7 @@ The following are optional as `step.with` keys | `discussion_category_name` | String | If specified, a discussion of the specified category is created and linked to the release. The value must be a category that already exists in the repository. For more information, see ["Managing categories for discussions in your repository."](https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | `generate_release_notes` | Boolean | Whether to automatically generate the name and body for this release. If name is specified, the specified name will be used; otherwise, a name will be automatically generated. If body is specified, the body will be pre-pended to the automatically generated notes. See the [GitHub docs for this feature](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes) for more information | | `append_body` | Boolean | Append to existing body instead of overwriting it | -| `make_latest` | Boolean | Whether to mark the release as latest or not. This defaults to true. | +| `make_latest` | Boolean | Whether to mark the release as latest or not. | 💡 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.