Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to list unadopted repositories in an administrative context. It is useful for administrators who want to retrieve and manage repositories that have not been adopted or claimed by any user or team within a Gitea instance. Typical use cases include auditing repository ownership, cleaning up unused repositories, or preparing reports on repository adoption status.

For example, an admin can use this node to fetch pages of unadopted repositories filtered by name patterns, helping them identify repositories that might need attention or reassignment.

Properties

Name Meaning
Page The page number of results to return (1-based). Allows pagination through the result set.
Limit The number of results per page (page size). Controls how many repositories are returned.
Pattern A string pattern to filter repositories by name. Only repositories matching this pattern will be listed.

Output

The node outputs JSON data representing a list of unadopted repositories retrieved from the Gitea API. Each item in the output typically contains details about a repository such as its name, description, creation date, and other metadata relevant to repository management.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • The node expects the base URL of the Gitea server to be configured in the credentials.
  • Uses the Gitea REST API endpoint /api/v1 to perform requests.

Troubleshooting

  • Common issues:
    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid page or limit values may result in empty responses or errors.
    • Network connectivity problems to the Gitea server will prevent data retrieval.
  • Error messages:
    • Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
    • HTTP 404 or 400 errors may indicate incorrect API endpoint usage or malformed query parameters; check property values.
    • Timeout or connection errors suggest network issues; ensure the Gitea server is reachable.

Links and References

Discussion