GiteaInstall

Overview

This node interacts with the Gitea API to delete a specific attachment from a release in a repository. It is useful when you want to programmatically manage release assets by removing outdated or incorrect attachments from a release in a Gitea-hosted repository.

Practical examples include:

• Automating cleanup of release attachments after a new release is published.
• Removing sensitive or deprecated files attached to a release.
• Managing release assets as part of a CI/CD pipeline.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the release attachment. Typically, this would confirm successful deletion or provide error details if the operation failed.

No binary data output is expected for this operation.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• Needs the base URL of the Gitea server configured in the credentials.
• Depends on the Gitea REST API being accessible and the user having sufficient permissions to delete release attachments.

Troubleshooting

• Common issues:

  • Invalid or missing repository owner or repo name can cause "Not Found" errors.
  • Incorrect release ID or attachment ID will result in failure to locate the resource.
  • Insufficient permissions or invalid API token may lead to authorization errors.
  • Network connectivity problems to the Gitea server can cause request failures.

• Error messages and resolutions:

  • 404 Not Found: Verify that the owner, repo, release ID, and attachment ID are correct.
  • 401 Unauthorized or 403 Forbidden: Check that the API key has the necessary permissions.
  • Network errors: Ensure the Gitea server URL is reachable and correct in credentials.

Links and References

• Gitea API Documentation - Releases
• Gitea Official Website