Support deleting existing releases

Extracted from 
This commit is contained in:
Naïm Favier 2021-12-04 18:07:48 +01:00
parent fe9a9bd329
commit ce037ed31d
No known key found for this signature in database
GPG key ID: 49B07322580B7EE2
6 changed files with 122 additions and 53 deletions

View file

@ -180,7 +180,8 @@ The following are optional as `step.with` keys
| `token` | String | Secret GitHub Personal Access Token. Defaults to `${{ github.token }}` |
| `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 existed body instead of overrides |
| `append_body` | Boolean | Whether to append to the existing body instead of overwriting. |
| `delete_on_existing` | Boolean | Whether or not to delete an existing release entirely when running this action. |
💡 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.