Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Commit Actions
- Tag Actions
Overview
This node interacts with the Forgejo API to manage releases within repositories. Specifically, the 'Delete' operation under the 'Release' resource allows users to delete a release by specifying the repository owner, repository name, and the release ID. This is useful for automating the cleanup or management of releases in a repository, such as removing outdated or incorrect releases.
Use Case Examples
- Deleting a release from a repository when it is no longer needed.
- Automating release management workflows by removing releases programmatically.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository where the release exists. |
| Repository | The name of the repository containing the release to delete. |
| Release ID | The unique identifier of the release to be deleted. |
Output
JSON
json- The JSON response from the Forgejo API after attempting to delete the release. Typically indicates success or failure of the deletion operation.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure that the 'Owner', 'Repository', and 'Release ID' fields are correctly specified and correspond to an existing release.
- If the API returns an error, verify that the API key credential has sufficient permissions to delete releases in the specified repository.
- Network issues or incorrect server URL in the credentials can cause request failures.