GiteaInstall

Overview

This node interacts with a Gitea server via its API, specifically allowing management of repository collaborators. The "Repo Delete Collaborator" operation removes a specified user from the list of collaborators on a given repository. This is useful for repository administrators who want to revoke access or manage team members programmatically.

Practical examples include:

• Automatically removing a collaborator when they leave a project.
• Cleaning up repository access as part of a CI/CD pipeline or administrative workflow.
• Managing permissions across multiple repositories in bulk.

Properties

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will be an empty response or a confirmation message indicating successful removal of the collaborator. No binary data output is expected.

Dependencies

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

Troubleshooting

• Common issues:
  • Invalid or missing API credentials can cause authentication failures.
  • Specifying a non-existent owner, repository, or collaborator username will result in errors.
  • Insufficient permissions for the authenticated user to modify repository collaborators.
• Error messages:
  • Authorization errors typically indicate invalid or expired API tokens.
  • Not found errors suggest incorrect owner, repo, or collaborator names.
  • Permission denied errors mean the authenticated user lacks rights to remove collaborators.
• Resolutions:
  • Verify and update API credentials.
  • Double-check spelling and existence of owner, repo, and collaborator.
  • Ensure the API user has admin or appropriate permissions on the repository.

Links and References

• Gitea API Documentation - Repository Collaborators
• Gitea Official Website