GiteaInstall

Overview

This node interacts with a Gitea repository to delete reviewers from a specific pull request. It is useful in scenarios where you want to programmatically manage pull request review assignments, such as removing individual or team reviewers from a pull request after changes have been made or when reviewers are no longer needed.

Practical examples include:

• Automatically cleaning up reviewers after a pull request has been updated.
• Removing reviewers who are no longer relevant to the review process.
• Managing review assignments in bulk via automation workflows.

Properties

Output

The node outputs JSON data representing the result of the delete operation on the pull request reviewers. This typically includes confirmation of the removal or details about the updated pull request state. There is no indication that binary data is output by this node.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• Needs the base URL of the Gitea server configured in credentials.
• Depends on the Gitea REST API endpoint /api/v1 to perform operations on repositories and pull requests.

Troubleshooting

• Common issues:

  • Incorrect repository owner or repo name may cause "not found" errors.
  • Providing an invalid pull request index can lead to failure in locating the pull request.
  • Malformed JSON in the Reviewers or Team Reviewers fields can cause parsing errors.
  • Insufficient permissions or missing API authentication token will result in authorization errors.

• Error messages and resolutions:

  • 404 Not Found: Verify the owner, repo, and pull request index values are correct.
  • 401 Unauthorized: Check that the API key credential is valid and has necessary permissions.
  • 400 Bad Request: Ensure the JSON arrays for reviewers and team reviewers are properly formatted.

Links and References

• Gitea API Documentation - Pull Requests
• Gitea Official Website