Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to replace all labels on a specific issue within a repository hosted on a Gitea instance. It is useful when you want to update the categorization or tagging of an issue by removing existing labels and setting new ones in bulk.

Common scenarios include:

  • Reorganizing issue labels after a change in project management strategy.
  • Correcting mislabeled issues by replacing incorrect labels with accurate ones.
  • Automating label updates based on external triggers or workflows.

For example, if an issue was initially tagged as "bug" but should be changed to "enhancement" and "priority-high," this operation will remove the old label and apply the new set.

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 to update labels for.
Labels A JSON array representing the new labels to set on the issue. Can be either:
- A list of integers (label IDs)
- A list of strings (label names)

Output

The node outputs the updated issue data in the json field. This typically includes the issue details reflecting the newly applied labels. The structure corresponds to the issue object returned by the Gitea API after label replacement.

No binary data output is expected from this operation.

Dependencies

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

Troubleshooting

  • Invalid repository or owner: Ensure that the owner and repo names are correct and accessible with the provided credentials.
  • Issue index not found: Verify that the issue number exists in the specified repository.
  • Labels format error: The labels property must be valid JSON representing either an array of label IDs or label names. Malformed JSON or unsupported formats will cause errors.
  • Authentication failures: Check that the API token is valid and has sufficient permissions to modify issues.
  • API rate limits or connectivity issues: Network problems or API restrictions may cause request failures; retry or check network settings.

Links and References

Discussion