GiteaInstall

Overview

This node interacts with the Gitea API to check if the current authenticated user is subscribed to a specific repository. It is useful in scenarios where you want to programmatically verify subscription status for notifications or updates on a repository within an automation workflow.

For example, you might use this node to:

• Automatically check if a user is watching a repository before sending them update notifications.
• Trigger different workflow branches depending on whether the user is subscribed to a repo.

Properties

Output

The node outputs JSON data representing the subscription status of the current user for the specified repository. This typically includes fields indicating whether the user is subscribed or not, and possibly additional metadata about the subscription.

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 user having appropriate permissions.

Troubleshooting

• Common issues:

  • Incorrect or missing API credentials will cause authentication failures.
  • Specifying a non-existent owner or repository will result in errors from the API.
  • Network connectivity problems to the Gitea server can cause request timeouts or failures.

• Error messages:

  • Authentication errors usually indicate invalid or expired API tokens; reconfigure credentials.
  • "Not Found" errors suggest the owner or repo does not exist or the user lacks access.
  • Rate limiting or permission denied errors require checking API usage limits and user rights.

Links and References

• Gitea API Documentation
• Gitea Official Website