Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea server via its API, specifically to check if a given user is a collaborator on a specified repository. It is useful in automation workflows where you need to verify user permissions or manage access control for repositories hosted on a Gitea instance.

Practical examples include:

  • Automatically verifying if a user has collaborator access before performing further actions like pushing code or managing issues.
  • Integrating with onboarding workflows to confirm that new team members have the correct repository access.
  • Auditing repository collaborators as part of security or compliance checks.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository to check.
Collaborator The username of the collaborator to verify.

Output

The node outputs JSON data indicating whether the specified user is a collaborator on the repository. The exact structure depends on the API response from the Gitea server but typically includes collaborator details or a status confirming their presence or absence.

If the node supports binary data output, it would generally relate to raw API responses or attachments, but this specific operation focuses on JSON data about repository collaborators.

Dependencies

  • Requires connection to a Gitea server with an API endpoint accessible.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL for the Gitea API must be set correctly in the credentials.

Troubleshooting

  • Common Issues:

    • Incorrect owner, repo, or collaborator names leading to "not found" errors.
    • Authentication failures due to missing or invalid API tokens.
    • Network connectivity problems preventing access to the Gitea server.
  • Error Messages:

    • 404 Not Found: The specified repository or collaborator does not exist. Verify the input values.
    • 401 Unauthorized: Authentication failed. Check the API token and credential configuration.
    • 500 Internal Server Error: Server-side issue; retry later or contact the Gitea administrator.

Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming network access.

Links and References

Discussion