Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve comments on issues within a specified repository. Specifically, the "Issue Get Repo Comments" operation fetches comments from all issues in a given repository, optionally filtered by update time and paginated.

Common scenarios where this node is useful include:

  • Monitoring discussions or feedback on issues across a repository.
  • Aggregating issue comments for reporting or analysis.
  • Triggering workflows based on new or updated comments in issues.

For example, you could use this node to pull all recent comments updated since yesterday to analyze user feedback or automate notifications when certain keywords appear in comments.

Properties

Name Meaning
Owner The owner (user or organization) of the repository from which to get issue comments.
Repo The name of the repository to query for issue comments.
Since Optional filter: only return comments updated since this timestamp (ISO 8601 format recommended).
Before Optional filter: only return comments updated before this timestamp.
Page The page number of results to return (1-based pagination).
Limit The number of comments to return per page (page size).

Output

The node outputs JSON data containing an array of issue comments retrieved from the specified repository. Each comment object typically includes details such as the comment body, author information, timestamps, and associated issue metadata.

If the API supports binary data for comments (e.g., attachments), the node would handle that accordingly, but based on the provided code and properties, the output focuses on JSON comment data.

Dependencies

  • Requires a valid API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in credentials.
  • Depends on the Gitea REST API being accessible and properly configured to allow fetching issue comments.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions to read issue comments.
  • Invalid repository or owner: Verify that the owner and repo names are correct and that the authenticated user has access.
  • Pagination issues: If no results are returned, check the Page and Limit parameters; setting them incorrectly may result in empty responses.
  • Date filters: The Since and Before fields should be in proper ISO 8601 date-time format; invalid formats might cause the API to ignore these filters or return errors.

Links and References

Discussion