Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to list repositories belonging to a specific team within an organization. It is useful for scenarios where you need to programmatically retrieve and manage repositories associated with teams, such as automating reporting, syncing repository data, or integrating team repo information into other workflows.

For example, you might use this node to:

  • Fetch all repositories of a development team to generate a status dashboard.
  • Automate access control by listing repos and updating permissions based on team membership.
  • Integrate team repository data into project management tools.

Properties

Name Meaning
Id The unique identifier of the team whose repositories you want to list (required).
Page The page number of results to return, starting at 1. Used for paginated responses.
Limit The number of results to return per page, controlling the page size in the response.

Output

The node outputs JSON data representing the list of repositories for the specified team. Each item in the output array corresponds to a repository object as returned by the Gitea API, typically including details like repository name, description, URL, visibility, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Relies on the Gitea REST API v1 endpoint /api/v1 to fetch team repositories.

Troubleshooting

  • Invalid Team ID: If the provided team ID does not exist or is incorrect, the API will likely return a 404 error. Verify the team ID before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
  • Pagination Issues: Setting page or limit to zero or negative values may result in unexpected behavior or errors. Use positive integers starting from 1 for page and a reasonable positive number for limit.
  • API Rate Limits: Frequent requests may hit rate limits imposed by the Gitea server. Implement retries or backoff strategies if needed.

Links and References

Discussion