Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node allows you to edit an existing pull request in a repository hosted on a Gitea server. It is useful for automating updates to pull requests such as changing the title, body, assignees, labels, or state without manually navigating the repository interface. For example, you can update the description of a pull request after receiving new feedback or change its status from open to closed programmatically.

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) identifying which pull request to edit
Allow Maintainer Edit Whether maintainers are allowed to modify the pull request
Assignee A single user assigned to the pull request
Assignees A JSON array of users assigned to the pull request
Base The base branch into which the pull request will be merged
Body The detailed description or content of the pull request
Due Date The due date for the pull request
Labels A JSON array of labels/tags associated with the pull request
Milestone The milestone number linked to the pull request
State The current state of the pull request (e.g., open, closed)
Title The title of the pull request
Unset Due Date Whether to remove the due date from the pull request

Output

The node outputs JSON data representing the updated pull request object returned by the Gitea API. This typically includes fields such as the pull request ID, title, body, state, assignees, labels, and other metadata reflecting the changes made. There is no binary output.

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 configuration.

Troubleshooting

  • Invalid repository or owner: Ensure the "Owner" and "Repo" names are correct and that the authenticated user has access.
  • Pull request index out of range: Verify the "Index" corresponds to an existing pull request number.
  • Permission errors: Confirm the API token has sufficient rights to edit pull requests.
  • Malformed JSON inputs: When providing JSON arrays (e.g., Assignees, Labels), ensure valid JSON syntax.
  • API connectivity issues: Check network access to the Gitea server and correct base URL in credentials.

Links and References

Discussion