Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to remove a specific label from an issue in a repository hosted on a Gitea instance. It is useful when managing issue labels programmatically, for example, to automate cleanup of outdated or incorrect labels on issues as part of your development workflow.

Practical examples include:

  • Automatically removing a "bug" label when an issue is resolved.
  • Cleaning up labels after an issue has been triaged or reassigned.
  • Integrating with CI/CD pipelines to update issue metadata based on build results.

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) of the issue from which the label should be removed.
Id The identifier of the label that needs to be removed from the issue.

Output

The node outputs JSON data representing the result of the label removal operation. This typically includes confirmation of the updated issue state or details about the removed label. No binary data output is involved.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Incorrect repository owner or repo name will cause the API call to fail.
    • Providing an invalid issue index or label ID may result in errors or no changes.
    • Authentication failures if the API token is missing or invalid.
  • Error Messages:

    • 404 Not Found: The specified issue or label does not exist. Verify the owner, repo, issue index, and label ID.
    • 401 Unauthorized: Authentication failed. Check the API token and permissions.
    • 400 Bad Request: Input parameters are invalid or missing. Ensure all required fields are correctly filled.

Resolving these usually involves verifying input values and ensuring proper API credentials are configured.

Links and References

Discussion