Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with a Gitea instance to list pull request reviews for a specific repository. It is useful when you want to programmatically retrieve review information on pull requests, such as comments, approvals, or change requests made by reviewers. Typical use cases include automating code review monitoring, generating reports on pull request activity, or integrating review data into other workflows.

For example, you might use this node to fetch all reviews for the 5th pull request in a repository owned by "octocat" named "hello-world", optionally paginating through results if there are many reviews.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the pull request exists.
Repo The name of the repository containing the pull request.
Index The index (number) of the pull request for which to list reviews.
Page (Optional) The page number of results to return, starting at 1. Used for pagination.
Limit (Optional) The number of results per page to return. Controls page size for pagination.

Output

The node outputs JSON data representing the list of pull request reviews retrieved from the Gitea API. Each item in the output corresponds to a single review and typically includes details such as reviewer identity, review state (approved, commented, etc.), timestamps, and review comments.

If the API supports it, the output may be paginated according to the Page and Limit input properties.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to a Gitea instance via its REST API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the credentials.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Invalid credentials or unauthorized access: Ensure the API token has sufficient permissions to read pull request reviews.
  • Repository or pull request not found: Verify that the Owner, Repo, and Index values correspond to existing resources in the Gitea instance.
  • Pagination issues: If no results appear, check that the Page and Limit parameters are correctly set; pages start at 1.
  • Network errors: Confirm that the Gitea server URL is reachable and correct in the credentials.
  • API rate limits: If many requests are made, the API might throttle calls; consider adding delays or handling rate limit responses.

Links and References

Discussion