Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea repository to submit a pull request review. It allows users to programmatically add reviews to pull requests, which is useful for automating code review workflows, integrating CI/CD pipelines, or managing repository contributions without manual intervention.

Typical use cases include:

  • Automatically submitting approval or change requests after automated tests pass.
  • Adding comments or feedback on pull requests as part of a bot-driven review process.
  • Integrating with external systems that trigger reviews based on custom logic.

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 to be reviewed.
Id The unique identifier of the specific review to submit or update.
Body The textual content of the review comment.
Event The state of the review event, indicating the type of review action (e.g., approve, request changes, comment).

Output

The node outputs JSON data representing the result of the pull request review submission. This typically includes details about the submitted review such as its ID, body content, state, and associated pull request information.

If binary data were involved (not indicated here), it would represent attachments or files related to the review, but this node focuses on JSON responses from the API.

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 for repository and pull request operations.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access the repository and submit reviews.
  • Invalid repository or owner: Verify that the owner and repo names are correct and accessible by the authenticated user.
  • Pull request not found: Confirm the pull request index corresponds to an existing open pull request.
  • Review ID issues: Make sure the review ID is valid and corresponds to a review that can be updated or submitted.
  • Event value errors: Use valid review event types supported by Gitea (such as "APPROVE", "REQUEST_CHANGES", or "COMMENT"). Invalid values may cause API rejections.

Links and References

Discussion