Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node integrates with the Gitea API to manage repositories and teams. Specifically, the "Repo Add Team" operation allows users to add a team to a repository within a Gitea instance. This is useful for automating repository access management by programmatically assigning teams to repositories, which can help streamline collaboration and permission control in development workflows.

Practical examples include:

  • Automatically adding a development team to new repositories created in an organization.
  • Managing team access across multiple repositories without manual intervention.
  • Integrating repository permissions setup into CI/CD pipelines.

Properties

Name Meaning
Owner The owner of the repository (user or organization name).
Repo The name of the repository to which the team will be added.
Team The name of the team to add to the repository.

Output

The node outputs JSON data representing the result of the API call to add a team to a repository. This typically includes confirmation details such as the team information and its association with the repository. The exact structure depends on the Gitea API response but generally confirms success or failure of the operation.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to a Gitea instance via its API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the Gitea API must be set in the credentials configuration.

Troubleshooting

  • Common issues:

    • Incorrect owner, repo, or team names may cause the API to return errors indicating that the resource was not found.
    • Insufficient permissions for the API token can lead to authorization errors.
    • Network connectivity problems between n8n and the Gitea server can cause request failures.
  • Error messages and resolutions:

    • 404 Not Found: Verify that the owner, repository, and team names are correct and exist in the Gitea instance.
    • 401 Unauthorized or 403 Forbidden: Check that the API token has sufficient permissions to modify repository teams.
    • Network errors: Ensure the Gitea server URL is reachable from the n8n environment and that no firewall or proxy is blocking the connection.

Links and References

Discussion