Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation retrieves a list of labels associated with a specific issue repository in Gitea, a self-hosted Git service. It is useful when you want to programmatically fetch all labels defined for issues within a particular repository, for example, to display them in a dashboard, automate label-based workflows, or synchronize labels with other systems.

Practical examples:

  • Fetching all issue labels from a project repository to populate a dropdown menu in a custom app.
  • Automating the synchronization of issue labels between Gitea and another issue tracking system.
  • Generating reports on label usage across repositories.

Properties

Name Meaning
Owner The username or organization name that owns the repository where the issue labels reside.
Repo The name of the repository from which to list the issue labels.
Page The page number of results to return (1-based). Useful for paginating through many labels.
Limit The maximum number of labels to return per page. Controls the page size of results.

Output

The node outputs JSON data containing an array of label objects retrieved from the specified repository. Each label object typically includes properties such as the label's name, color, and description (depending on Gitea's API response structure).

If the node supports binary data output, it would be related to any attachments or images associated with labels, but based on the provided code and operation, the output is purely JSON with label details.

Dependencies

  • Requires access to a Gitea instance via its REST API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials.
  • Pagination parameters (page and limit) are supported to control the volume of data returned.

Troubleshooting

  • Common Issues:

    • Incorrect owner or repository names will result in errors or empty responses.
    • Missing or invalid API authentication token will cause authorization failures.
    • Pagination parameters out of range may lead to empty results.

  • Error Messages:

    • Unauthorized or 401 errors indicate missing or invalid API credentials.
    • 404 Not Found errors suggest the specified repository or owner does not exist.
    • Rate limiting errors may occur if too many requests are made in a short time; retry after some delay.

  • Resolutions:

    • Verify the owner and repo names are correct and accessible by the API user.
    • Ensure the API key/token is valid and has sufficient permissions.
    • Adjust pagination parameters to valid ranges.
    • Check network connectivity to the Gitea server.

Links and References

Discussion