Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve labels associated with a specific issue in a repository. It is useful when you want to programmatically fetch all labels assigned to an issue, for example, to analyze issue categorization, automate workflows based on labels, or display label information in dashboards.

Practical examples:

  • Automatically fetching labels of an issue to trigger different automation paths depending on the label.
  • Aggregating label data from multiple issues for reporting purposes.
  • Syncing issue labels with other project management tools.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the issue is.
Repo The name of the repository containing the issue.
Index The index (number) of the issue whose labels you want to retrieve.

Output

The node outputs JSON data representing the labels attached to the specified issue. Each label typically includes properties such as its name, color, and description (depending on the Gitea API response). This output can be used downstream in workflows for further processing or decision-making.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea REST API being accessible and the user having permission to read issue data.

Troubleshooting

  • Common issues:

    • Incorrect repository owner or repo name will result in errors or empty results.
    • Providing an invalid or out-of-range issue index may cause the API to return an error.
    • Network connectivity problems or incorrect API URL configuration can prevent successful requests.
  • Error messages:

    • Authentication errors indicate missing or invalid API credentials; ensure the API key is correct and has sufficient permissions.
    • "Issue not found" or similar errors suggest the issue index does not exist in the specified repo.
    • Rate limiting or server errors require checking API usage limits or server status.

Links and References

Discussion