Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance via its API to list pinned pull requests for a specified repository. It is useful when you want to quickly retrieve highlighted or important pull requests that have been pinned in a repository, for example, to monitor key contributions or ongoing work that the repository maintainers want to emphasize.

Practical examples include:

  • Displaying pinned pull requests on a dashboard.
  • Automating notifications or reports about important pull requests.
  • Integrating pinned pull request data into other workflows or tools.

Properties

Name Meaning
Owner The owner (user or organization) of the repository.
Repo The name of the repository from which to list pinned pull requests.

Output

The node outputs JSON data representing the list of pinned pull requests for the specified repository. Each item in the output typically contains details about a pull request such as its title, author, status, and other metadata as provided by the Gitea API.

If the node supports binary data output, it would be related to attachments or files associated with pull requests, but based on the provided code snippet, the primary output is JSON.

Dependencies

  • Requires access to a Gitea instance with an API endpoint.
  • Needs an API authentication token or API key credential configured in n8n to authenticate requests.
  • The base URL for the Gitea API must be set in the credentials configuration.

Troubleshooting

  • Common issues:
    • Incorrect or missing repository owner or name will result in errors or empty results.
    • Authentication failures if the API key or token is invalid or missing.
    • Network connectivity issues to the Gitea server.
  • Error messages:
    • Unauthorized or 401 errors indicate problems with API credentials.
    • 404 errors suggest the repository or resource does not exist or is inaccessible.
    • Timeout or network errors indicate connectivity problems.
  • Resolutions:
    • Verify the owner and repo names are correct.
    • Ensure the API key/token is valid and has sufficient permissions.
    • Check network access to the Gitea server.

Links and References

Discussion