Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance to retrieve detailed information about a specific pull request review within a repository. It is useful when you want to programmatically access the review comments, status, or metadata of a particular pull request review in a Gitea-managed repository. For example, it can be used in automation workflows that monitor code reviews, trigger notifications based on review outcomes, or aggregate review data for reporting.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository where the pull request exists.
Index The index (number) of the pull request within the repository (usually the PR number).
Id The unique identifier of the specific pull request review to retrieve.

Output

The node outputs JSON data representing the details of the specified pull request review. This typically includes information such as the review's author, state (e.g., approved, commented), body text, timestamps, and any other metadata provided by the Gitea API for pull request reviews.

If the node supports binary data output, it would generally relate to attachments or files associated with the review, but this is not indicated in the provided source.

Dependencies

  • Requires an active connection to a Gitea instance via its API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials configuration.

Troubleshooting

  • Common Issues:

    • Incorrect repository owner or name may lead to "Not Found" errors.
    • Providing an invalid pull request index or review ID will result in failure to retrieve data.
    • Authentication failures if the API token is missing or invalid.
    • Network connectivity issues to the Gitea server.
  • Error Messages:

    • 404 Not Found: Check that the owner, repo, pull request index, and review ID are correct.
    • 401 Unauthorized: Verify that the API authentication token is correctly configured and has sufficient permissions.
    • Network Errors: Ensure the Gitea server URL is reachable from the n8n environment.

Links and References

Discussion