Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation retrieves comments and timeline events for a specific issue in a repository hosted on a Gitea instance. It is useful when you want to gather detailed discussion history and activity logs related to an issue, such as comments made by collaborators or status changes over time.

Practical examples include:

  • Monitoring ongoing discussions on a bug report or feature request.
  • Aggregating all timeline events for audit or reporting purposes.
  • Fetching recent comments updated since a certain date to track new feedback.

Properties

Name Meaning
Owner The owner (user or organization) of the repository containing the issue.
Repo The name of the repository where the issue exists.
Index The index (number) identifying the specific issue within the repository.
Since Optional. If provided, only comments updated since this timestamp are returned.
Page Optional. The page number of results to return (1-based pagination).
Limit Optional. The number of results per page (page size).
Before Optional. If provided, only comments updated before this timestamp are returned.

Output

The output JSON contains an array of comment and timeline event objects associated with the specified issue. Each object typically includes details such as the comment content, author information, timestamps, and event types describing actions taken on the issue (e.g., status changes, assignments).

If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses on textual and event data only.

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 for the Gitea API must be set in the credentials configuration.

Troubleshooting

  • Common issues:

    • Incorrect repository owner or name will result in "Not Found" errors.
    • Providing invalid timestamps for Since or Before parameters may cause query failures.
    • Pagination parameters (Page, Limit) set to zero or negative values might lead to unexpected results or errors.
  • Error messages:

    • 404 Not Found: Verify that the owner, repo, and issue index are correct.
    • 401 Unauthorized: Check that the API authentication token is valid and has sufficient permissions.
    • 400 Bad Request: Ensure that date/time strings for filtering are correctly formatted (ISO 8601 recommended).

Links and References

Discussion