Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve information about repository assignees. Specifically, for the "Repository" resource and the "Repo Get Assignees" operation, it fetches the list of users who can be assigned issues in a given repository. This is useful in automation workflows where you need to dynamically obtain potential assignees for issue tracking or task assignment within a Gitea repository.

Practical examples include:

  • Automatically fetching assignees to assign new issues created via n8n.
  • Generating reports or notifications based on available assignees in a repository.
  • Integrating with other tools that require knowledge of repository collaborators.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository from which to get assignees.

Both properties are required string inputs.

Output

The node outputs JSON data containing the list of assignees for the specified repository. Each item in the output typically represents a user object with details such as username, id, and other metadata provided by the Gitea API.

If the node supports binary data output (not indicated here), it would generally relate to file downloads or attachments, but this operation focuses solely on JSON data representing users.

Dependencies

  • Requires an active connection to a Gitea instance via its API.
  • Needs an API authentication token or key 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 owner or repo names will result in errors or empty results.
    • Missing or invalid API credentials will cause authentication failures.
    • Network connectivity problems to the Gitea server will prevent data retrieval.
  • Error Messages:

    • Authentication errors usually indicate invalid or missing API tokens; verify credentials.
    • "Not Found" errors suggest the repository or owner does not exist or is inaccessible.
    • Rate limiting or permission errors may occur if the API token lacks sufficient rights.

Resolving these typically involves verifying input parameters, checking credential validity, and ensuring proper permissions on the Gitea server.

Links and References

Discussion