Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to remove an issue blocking relationship from a specific issue in a repository hosted on a Gitea instance. In practical terms, it is used when you want to indicate that one issue no longer blocks the progress of another issue by removing the blocking link between them.

Common scenarios include:

  • Managing issue dependencies in project tracking where issues block each other.
  • Updating issue relationships after changes in project priorities or resolutions.
  • Automating cleanup of issue blockers during workflow automation.

For example, if Issue A was previously blocking Issue B, and now that dependency is resolved or invalid, this operation removes that blocker link from Issue B.

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 to remove the blocking.

Output

The output JSON will typically contain the response from the Gitea API confirming the removal of the issue blocking relationship. This may include details about the updated issue or a success status. No binary data output is expected.

Dependencies

  • Requires connection to a Gitea instance via its API.
  • Needs an API authentication token credential configured in n8n for accessing the Gitea API.
  • The base URL of the Gitea server must be set in the credentials.

Troubleshooting

  • Invalid repository or owner: Ensure the "Owner" and "Repo" fields are correctly specified and that the authenticated user has access rights.
  • Issue index not found: Verify the issue index number corresponds to an existing issue in the repository.
  • Authentication errors: Confirm that the API key/token is valid and has sufficient permissions.
  • API connectivity issues: Check network connectivity to the Gitea server and that the base URL is correct.

Links and References

Discussion