GiteaInstall

Overview

This node interacts with the Gitea API to check whether a specific issue in a repository is subscribed to by the authenticated user. It is useful for workflows that need to verify subscription status on issues, such as triggering notifications or conditional logic based on whether the user is watching an issue.

A practical example would be automating alerts only if the user is subscribed to an issue or managing subscriptions programmatically.

Properties

Output

The output JSON will contain information about the subscription status of the specified issue. Typically, this includes whether the authenticated user is subscribed to the issue or not. The exact structure depends on the Gitea API response but generally indicates subscription details related to the issue.

No binary data output is expected from this operation.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• The node uses the Gitea REST API v1 endpoint configured via credentials.
• The base URL for the Gitea API must be set in the node credentials.

Troubleshooting

• Common Issues:

  • Incorrect repository owner or repo name can lead to "Not Found" errors.
  • Invalid or missing API authentication token will cause authorization failures.
  • Specifying an invalid issue index may result in errors or empty responses.

• Error Messages:

  • 404 Not Found: Check that the owner, repo, and issue index are correct.
  • 401 Unauthorized: Verify that the API key credential is valid and has sufficient permissions.
  • 400 Bad Request: Ensure all required parameters are provided and correctly formatted.

Links and References

• Gitea API Documentation
• Gitea Issues API (for subscription checking endpoints)