GiteaInstall

Overview

This node interacts with the Gitea API to delete an issue from a specified repository. It is useful in automation workflows where you need to programmatically remove issues, for example, cleaning up outdated or invalid issues, or managing issue lifecycle based on external triggers.

A practical example would be automatically deleting issues that are marked as duplicates or resolved in another system, helping maintain a clean issue tracker without manual intervention.

Properties

Output

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

No binary data output is involved.

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 authenticated user having permission to delete issues in the specified repository.

Troubleshooting

• Common Issues:

  • Incorrect owner or repo names can cause "Not Found" errors.
  • Insufficient permissions may result in authorization errors.
  • Providing an invalid issue index (e.g., non-existent issue number) will fail to delete.

• Error Messages:

  • 404 Not Found: Check that the owner, repo, and issue index are correct.
  • 401 Unauthorized or 403 Forbidden: Verify that the API key has sufficient rights.
  • 400 Bad Request: Ensure the issue index is a valid number.

Resolving these typically involves verifying input parameters and ensuring proper API credentials and permissions.

Links and References

• Gitea API Documentation - Issues
• Gitea Official Website