GiteaInstall

Overview

This node interacts with a Gitea instance via its API to retrieve information about a specific commit's pull request in a repository. It is useful when you want to programmatically fetch details about the pull request associated with a particular commit SHA in a given repository. For example, it can be used in automation workflows that track code changes, trigger CI/CD pipelines based on pull requests, or gather metadata for reporting purposes.

Properties

Output

The node outputs JSON data representing the pull request associated with the specified commit SHA. This typically includes details such as pull request ID, title, description, author, status, and other metadata returned by the Gitea API. If the commit is not linked to any pull request, the output may be empty or indicate no association.

No binary data output is produced by this node.

Dependencies

• Requires an active connection to a Gitea instance.
• Needs an API authentication token configured in the node credentials to authorize API requests.
• The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Incorrect repository owner or name will result in "not found" errors.
  • Providing an invalid or non-existent commit SHA will lead to errors or empty results.
  • Network connectivity problems to the Gitea server can cause request timeouts or failures.

• Error messages and resolutions:

  • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
  • 404 Not Found: Verify the owner, repo, and commit SHA values are correct.
  • Timeouts or network errors: Ensure the Gitea server URL is reachable from n8n and there are no firewall restrictions.

Links and References

• Gitea API Documentation
• Gitea Official Website