Overview

This node interacts with the Forgejo API to list issues in a specified repository. It supports filtering issues by their state (open, closed, or all) and allows pagination through additional options such as page number and limit per page. This node is useful for retrieving issue data for project management, reporting, or automation workflows involving issue tracking in Forgejo repositories.

Use Case Examples

1. List all open issues in a repository owned by a specific user or organization.
2. Retrieve closed issues for a repository to analyze resolved tasks.
3. Fetch a limited number of issues per page to handle large repositories efficiently.

Properties

Output

JSON

• json
  • ``
    * id - Unique identifier of the issue.
    * title - Title of the issue.
    * state - Current state of the issue (open or closed).
    * body - Detailed description or body content of the issue.
    * labels - Labels associated with the issue.
    * assignees - Users assigned to the issue.
    * created_at - Timestamp when the issue was created.
    * updated_at - Timestamp when the issue was last updated.

Dependencies

• Forgejo API

Troubleshooting

• Ensure the API credentials for Forgejo are correctly configured and have the necessary permissions to access repository issues.
• Verify that the 'owner' and 'repository' parameters are correctly set to valid values to avoid 404 errors.
• If pagination parameters are set, ensure they are within valid ranges to prevent empty or incomplete results.
• Common error messages include authentication failures, invalid repository or owner names, and rate limiting by the Forgejo API. Resolving these typically involves checking credentials, input parameters, and API usage limits.

Links

• Forgejo API Documentation - Official documentation for the Forgejo API endpoints and usage.