GiteaInstall

Overview

This node interacts with a Gitea instance via its API, specifically allowing users to delete a topic from a repository. It is useful in scenarios where repository topics need to be managed programmatically, such as cleaning up outdated or irrelevant topics from repositories in bulk or as part of automated workflows.

For example, if you have a repository tagged with several topics and want to remove one that is no longer relevant, this node can perform that deletion automatically based on the specified owner, repository name, and topic.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the specified topic. Typically, this would confirm whether the deletion was successful or provide error details if it failed.

No binary data output is expected from this operation.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• The node expects the base URL of the Gitea server to be configured in the credentials.
• Uses the Gitea REST API v1 endpoint /api/v1.

Troubleshooting

• Common issues:
  • Incorrect owner or repository name may cause "not found" errors.
  • Trying to delete a topic that does not exist will likely result in an error response.
  • Authentication failures if the API key or URL is misconfigured.
• Error messages:
  • Unauthorized or forbidden errors indicate invalid or missing API credentials.
  • Not found errors suggest the owner, repo, or topic does not exist or is misspelled.
• Resolutions:
  • Verify the correctness of the owner, repo, and topic names.
  • Ensure the API key credential has sufficient permissions.
  • Confirm the Gitea base URL is correct and accessible.

Links and References

• Gitea API Documentation (for general API reference)
• Gitea Repository Topics API (specific endpoint for deleting topics)