Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation allows you to list issues from a specified repository in Gitea, a self-hosted Git service. It is useful for retrieving and filtering issues based on various criteria such as state (open, closed, or all), labels, milestones, and user involvement. This can help automate workflows that involve issue tracking, reporting, or integration with other tools.

Practical examples:

  • Fetching all open issues assigned to a specific user to generate a task list.
  • Retrieving issues updated within a certain timeframe for status reporting.
  • Filtering issues by labels or milestones to monitor progress on specific features or bug fixes.

Properties

Name Meaning
Owner The owner of the repository from which to list issues.
Repo The name of the repository.
State Filter issues by their state: Closed, Open, or All.
Labels Comma-separated list of labels to filter issues. Only issues with any of these labels are fetched.
Q Search string to filter issues by text query.
Type Filter by type: Issues or Pulls.
Milestones Comma-separated list of milestone names or IDs to filter issues.
Since Show only items updated after this timestamp (RFC 3339 format).
Before Show only items updated before this timestamp (RFC 3339 format).
Created By Show only items created by the specified user.
Assigned By Show only items assigned to the specified user.
Mentioned By Show only items where the specified user was mentioned.
Page Page number of results to return (1-based).
Limit Number of results per page (page size).

Output

The output contains a JSON array of issue objects retrieved from the Gitea API. Each object represents an issue or pull request (depending on the Type filter) with details such as title, state, labels, assignees, milestones, timestamps, and other metadata.

If binary data were involved (e.g., attachments), it would be summarized here, but this operation deals solely with JSON issue data.

Dependencies

  • Requires connection to a Gitea instance via its API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials.

Troubleshooting

  • Common issues:

    • Incorrect repository owner or name will result in no data or errors.
    • Invalid or missing API credentials will cause authentication failures.
    • Using unsupported or misspelled filter values may lead to empty results.
    • Pagination parameters (Page and Limit) set incorrectly might skip or limit results unexpectedly.

  • Error messages:

    • Authentication errors typically indicate invalid or missing API tokens; verify credentials.
    • "Not Found" errors usually mean the repository does not exist or access is denied.
    • Rate limiting errors may occur if too many requests are made in a short time; wait and retry.

Links and References

Discussion