Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to remove dependencies from a specific issue in a repository hosted on a Gitea instance. It is useful when managing issue relationships, such as unlinking issues that were previously marked as dependent on one another. For example, if an issue was mistakenly set as blocking another or if the dependency is no longer relevant, this operation helps maintain accurate issue tracking by removing those links.

Properties

Name Meaning
Owner The owner (user or organization) of the repository containing the issue.
Repo The name of the repository where the issue exists.
Index The index (number) identifying the specific issue from which dependencies will be removed.

Output

The output JSON typically contains the response from the Gitea API confirming the removal of the issue dependencies. This may include updated issue data or a status message indicating success. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires access to a Gitea instance with API enabled.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the Gitea API must be set in the node credentials.
  • The node uses the Gitea REST API v1 endpoints.

Troubleshooting

  • Invalid Owner/Repo/Index: If the owner, repo, or issue index is incorrect or does not exist, the API will return an error. Verify these values carefully.
  • Authentication Errors: Missing or invalid API tokens will cause authorization failures. Ensure the API key credential is correctly configured.
  • Permission Issues: The authenticated user must have sufficient permissions to modify issues in the repository.
  • API Endpoint Changes: If the Gitea API version changes, the node might fail. Confirm compatibility with your Gitea server version.

Links and References

Discussion