Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve the permission level of a specific collaborator on a given repository. It is useful in scenarios where you need to programmatically check what access rights a user has on a repository, such as read, write, or admin permissions. For example, it can be used in automation workflows that manage repository access control or audit collaborator permissions before performing actions.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository for which to check collaborator permissions.
Collaborator The username of the collaborator whose permissions you want to retrieve.

Output

The node outputs JSON data containing the permission details of the specified collaborator on the repository. This typically includes fields indicating the level of access (e.g., read, write, admin) the collaborator has. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea REST API being accessible and the authenticated user having sufficient rights to query collaborator permissions.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect owner, repo, or collaborator names may result in "not found" errors.
    • Insufficient permissions of the authenticated user to view collaborator permissions can lead to authorization errors.
  • Error messages:
    • 401 Unauthorized: Check that the API key is valid and has necessary scopes.
    • 404 Not Found: Verify that the owner, repository, and collaborator usernames are correct.
    • 403 Forbidden: Ensure the authenticated user has permission to access collaborator information.

Links and References

Discussion