GiteaInstall

Overview

This node allows users to delete a repository from a Gitea instance via its API. It is useful in automation workflows where repositories need to be programmatically removed, such as cleaning up test repositories, managing project lifecycle, or integrating repository management into CI/CD pipelines.

For example, you might use this node to automatically delete a repository after a project is archived or when a cleanup job runs periodically to remove unused repositories.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the repository. Typically, for a successful deletion, the output may be empty or contain confirmation details depending on the API's response. No binary data is produced by this operation.

Dependencies

• Requires an API key credential with access rights to the Gitea instance.
• The node communicates with the Gitea API endpoint configured in the credentials.
• Proper permissions are necessary to delete repositories on the target Gitea server.

Troubleshooting

• Common issues:

  • Insufficient permissions: The API token used must have rights to delete repositories.
  • Incorrect owner or repo name: Ensure these values exactly match the repository to delete.
  • Network or authentication errors: Verify the base URL and API credentials are correct.

• Error messages:

  • Authorization errors typically indicate invalid or insufficient credentials.
  • Not found errors suggest the specified repository does not exist under the given owner.
  • Rate limiting or server errors should be handled by retrying or checking server status.

Links and References

• Gitea API Documentation - Repository Delete (official API reference)
• Gitea Official Website