GitHub Issues icon

GitHub Issues

Consume issues from the GitHub API
Join our community

Actions4

Overview

This node interacts with the GitHub API to retrieve multiple issues from a specified repository. It is useful for scenarios where users need to fetch a list of issues for project management, reporting, or integration with other tools. For example, a user can get all open issues updated since a certain date or limit the number of issues retrieved for analysis.

Use Case Examples

  1. Fetch all open issues from a specific GitHub repository to monitor ongoing tasks.
  2. Retrieve issues updated since a particular date to track recent changes or bug reports.

Properties

Name Meaning
Authentication Method of authenticating with GitHub API, either via Access Token or OAuth2.
Repository Owner The owner of the GitHub repository from which to fetch issues. Can be selected from a list, provided as a URL, or entered by name.
Repository Name The name of the GitHub repository from which to fetch issues. Can be selected from a list, provided as a URL, or entered by name.
Limit Maximum number of issues to return when not returning all results.
Return All Whether to return all issues or limit the number of results.
Filters Optional filters to refine the issues retrieved, such as state (open, closed, all) and updated since a specific date.

Output

JSON

  • id - Unique identifier of the issue.
  • number - Issue number within the repository.
  • title - Title of the issue.
  • state - Current state of the issue (open or closed).
  • created_at - Timestamp when the issue was created.
  • updated_at - Timestamp when the issue was last updated.
  • closed_at - Timestamp when the issue was closed, if applicable.
  • user
    • login - Username of the issue creator.
  • assignees - List of users assigned to the issue.
  • labels - Labels associated with the issue.
  • body - Detailed description or content of the issue.

Dependencies

  • GitHub API
  • API authentication via Access Token or OAuth2

Troubleshooting

  • Ensure the authentication credentials (Access Token or OAuth2) are valid and have the necessary permissions to access repository issues.
  • Verify that the repository owner and name are correctly specified and accessible with the provided credentials.
  • If using URL mode for owner or repository, ensure the URL format matches the expected GitHub URL pattern.
  • When using pagination (Return All), be aware of GitHub API rate limits and handle potential rate limit errors by implementing retries or delays.

Links

Discussion