Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows users to cancel a scheduled auto-merge for a specific pull request in a repository hosted on a Gitea instance. It is useful when an automatic merge of a pull request has been planned but needs to be aborted before it occurs, for example, if new issues are found or the merge conditions have changed.

Practical scenarios include:

  • Halting an automated merge process triggered by CI/CD pipelines.
  • Managing pull requests where scheduled merges need manual intervention.
  • Integrating with workflows that require conditional cancellation of merges based on external events.

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) identifying the pull request to cancel the auto-merge for.

Output

The node outputs JSON data representing the result of the cancel auto-merge operation. This typically includes confirmation of the cancellation or details about the pull request's updated state after the cancellation.

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

  • Invalid owner or repo name: Ensure the "Owner" and "Repo" properties exactly match the repository details on the Gitea server.
  • Incorrect pull request index: The "Index" must correspond to an existing pull request number; otherwise, the operation will fail.
  • Authentication errors: Verify that the API key or token used has sufficient permissions to modify pull requests.
  • Network or connectivity issues: Confirm that the Gitea server URL is reachable from the n8n environment.

Common error messages might include unauthorized access, not found errors for the pull request, or validation errors for input parameters. Resolving these involves checking credentials, input values, and network settings.

Links and References

Discussion