PATCH /repos/{owner}/{repo}/releases/{release_id}
Users with push access to the repository can edit a release.
Servers
- https://api.github.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
repo |
String | Yes |
The name of the repository without the |
release_id |
Integer | Yes |
The unique identifier of the release. |
owner |
String | Yes |
The account owner of the repository. The name is not case sensitive. |
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
target_commitish |
String | No |
Specifies the commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. Unused if the Git tag already exists. Default: the repository's default branch. |
draft |
Boolean | No |
|
make_latest |
String | No |
Specifies whether this release should be set as the latest release for the repository. Drafts and prereleases cannot be set as latest. Defaults to Possible values:
Default value: "true" |
tag_name |
String | No |
The name of the tag. |
name |
String | No |
The name of the release. |
body |
String | No |
Text describing the contents of the tag. |
prerelease |
Boolean | No |
|
discussion_category_name |
String | No |
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. If there is already a discussion linked to the release, this parameter is ignored. For more information, see "Managing categories for discussions in your repository." |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.