Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation retrieves a list of milestones from a specified repository in Gitea. It is useful for workflows that need to fetch milestone data for project management, reporting, or automation purposes related to issue tracking. For example, you might use this node to get all open milestones in a repo to display progress or to trigger actions based on milestone states.

Properties

Name Meaning
Owner The owner (user or organization) of the repository from which to fetch milestones.
Repo The name of the repository to query for milestones.
State Filter milestones by their state. Options: open, closed, or all. Defaults to open.
Name Filter milestones by milestone name (exact match).
Page The page number of results to return (1-based pagination).
Limit The number of results per page (page size).

Output

The node outputs JSON data containing an array of milestone objects retrieved from the specified repository. Each milestone object typically includes details such as milestone title, description, state, due date, and other metadata relevant to the milestone in Gitea.

No binary data output is involved in 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 for the Gitea API must be set in the credentials configuration.

Troubleshooting

  • Common issues:
    • Incorrect or missing repository owner or name will result in errors or empty results.
    • Invalid or expired API credentials will cause authentication failures.
    • Pagination parameters (page and limit) set incorrectly may lead to unexpected result counts or empty responses.
  • Error messages:
    • Authentication errors indicate problems with the API key/token; verify and update credentials.
    • "Not Found" errors usually mean the repository or milestones do not exist or are inaccessible; check spelling and permissions.
    • Rate limiting errors may occur if too many requests are made in a short time; implement retry logic or reduce request frequency.

Links and References

Discussion