Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance via its API, specifically to retrieve pull request review comments for a given repository. It is useful when you want to programmatically access detailed feedback left on pull requests, such as during code reviews or collaboration workflows.

A practical example would be automating the collection of all review comments on a specific pull request to generate reports, trigger notifications, or integrate with other tools like issue trackers or chat platforms.

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 within the repository (usually the pull request ID).
Id The unique identifier of the specific review whose comments you want to retrieve.

Output

The node outputs JSON data representing the list of review comments associated with the specified pull request review. Each comment typically includes details such as the comment text, author information, timestamps, and possibly line references in the code.

No binary data output is indicated by the source code.

Dependencies

  • Requires an active connection to a Gitea instance.
  • 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 configuration.

Troubleshooting

  • Common issues:
    • Incorrect repository owner or name may result in "Not Found" errors.
    • Invalid or missing API authentication token will cause authorization failures.
    • Providing an invalid pull request index or review ID can lead to empty results or errors.
  • Error messages:
    • Authorization errors indicate problems with the API key or permissions.
    • Resource not found errors suggest incorrect input parameters or that the resource does not exist.
  • Resolutions:
    • Verify all input properties carefully.
    • Ensure the API token has sufficient permissions to read pull request data.
    • Confirm the pull request and review IDs exist in the target repository.

Links and References

Discussion