Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to add a subscription for a user to a specific issue in a repository hosted on a Gitea instance. Subscribing a user to an issue means that the user will receive notifications or updates related to that issue. This is useful in collaborative development environments where team members want to stay informed about progress, comments, or changes on particular issues.

Practical examples:

  • Automatically subscribing a QA team member to newly created bug reports so they get notified of any updates.
  • Adding a project manager as a subscriber to critical issues to keep track of their resolution status.
  • Enabling users to subscribe themselves to issues they are interested in following.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the issue exists.
Repo The name of the repository containing the issue.
Index The index (number) identifying the specific issue within the repository.
User The username of the user to be subscribed to the issue.

Output

The node outputs JSON data representing the result of the subscription addition request. Typically, this includes confirmation details such as the subscription status or the subscribed user's information related to the issue.

If the API supports it, the output may also include metadata about the issue or subscription, but no binary data output is expected from this operation.

Dependencies

  • Requires access to a Gitea instance with API enabled.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL of the Gitea server must be provided in the credentials configuration.
  • The node uses the Gitea REST API endpoint for managing issue subscriptions.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials can cause authorization failures.
    • Incorrect repository owner or repo name will lead to "not found" errors.
    • Providing an invalid issue index (e.g., non-existent issue number) will result in errors.
    • Attempting to subscribe a user who does not exist or lacks permission may fail.
  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key/token is valid and has sufficient permissions.
    • 404 Not Found: Verify the owner, repo, and issue index values are correct.
    • 400 Bad Request: Ensure all required parameters are provided and correctly formatted.
    • 403 Forbidden: Confirm that the authenticated user has rights to manage subscriptions on the repository.

Links and References

Discussion