GiteaInstall

Overview

This node interacts with a Gitea server via its API to list all teams associated with a specific repository. It is useful for scenarios where you need to manage or audit team access and permissions on repositories within an organization or user account hosted on Gitea. For example, a DevOps engineer might use this node to retrieve the teams that have access to a repository before modifying permissions or automating team management workflows.

Properties

Output

The node outputs JSON data representing the list of teams associated with the specified repository. Each item in the output typically contains details about a team such as its ID, name, description, permission level, and other metadata provided by the Gitea API. There is no binary data output.

Dependencies

• Requires connection to a Gitea instance.
• 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 owner or repository names will result in errors or empty results.
  • Authentication failures if the API token is invalid or lacks sufficient permissions.
  • Network connectivity problems to the Gitea server.
• Error messages:
  • Unauthorized or 401 errors indicate invalid or missing API credentials.
  • 404 errors suggest the repository or owner does not exist or is inaccessible.
  • Rate limiting or 429 errors may occur if too many requests are made in a short time; retry after some delay.

Links and References

• Gitea API Documentation - Repository Teams
• Gitea Official Website