Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to list content blocks of a specific issue within a repository. It is useful when you want to programmatically retrieve detailed structured data (blocks) from an issue, such as comments, code snippets, or other block elements that make up the issue's content.

Typical use cases include:

  • Automating issue analysis by extracting and processing individual blocks.
  • Integrating issue content into other systems or workflows.
  • Generating reports or summaries based on issue content structure.

For example, you might use this node to fetch all comment blocks from a particular issue in a repository to analyze user feedback or track discussion threads.

Properties

Name Meaning
Owner The owner of the repository where the issue exists.
Repo The name of the repository containing the issue.
Index The index (number) of the issue for which to list blocks.
Page (Optional) The page number of results to return, starting at 1. Used for pagination.
Limit (Optional) The number of results per page to return. Controls page size for pagination.

Output

The node outputs JSON data representing the blocks of the specified issue. Each block corresponds to a distinct part of the issue content, such as text sections, code snippets, or other structured elements defined by Gitea's API.

If the issue contains multiple blocks, the output will be paginated according to the Page and Limit parameters.

No binary data output is indicated by the source code.

Dependencies

  • Requires access to a Gitea instance via its REST API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the Gitea API must be set in the node credentials.

Troubleshooting

  • Invalid Owner/Repo/Index: If the specified repository owner, repository name, or issue index is incorrect or does not exist, the node will fail to retrieve data. Verify these inputs carefully.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly configured.
  • Pagination Issues: Setting Page or Limit to zero or negative values may result in unexpected behavior or errors. Use positive integers.
  • API Rate Limits: Frequent calls to the Gitea API may hit rate limits; handle such errors by implementing retries or backoff strategies.

Links and References

Discussion