Overview
The "GitHub Issues" node allows users to interact with GitHub's issue tracking system via the GitHub API. Specifically, the "Get Many" operation under the "Issue" resource fetches multiple issues from a specified GitHub repository. This is useful for scenarios such as monitoring open or closed issues, generating reports on issue activity, or integrating issue data into other workflows.
Practical examples include:
- Retrieving all open issues in a project to display in a dashboard.
- Fetching recently updated issues since a certain date to trigger notifications.
- Collecting closed issues for archival or analysis purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with GitHub API. Options: "Access Token" (personal access token) or "OAuth2" (OAuth 2.0 authentication). |
| Repository Owner | The owner of the GitHub repository. Can be selected from a list of users, provided as a GitHub URL, or entered by name. |
| Repository Name | The name of the GitHub repository. Can be selected from a list of repositories, provided as a GitHub URL, or entered by name. |
| Return All | Boolean flag indicating whether to return all matching issues or limit the number of results. |
| Limit | When "Return All" is false, this sets the maximum number of issues to return (1 to 100). |
| Filters | Collection of filters to narrow down the issues returned: |
| - Updated Since | Date/time filter to return only issues updated at or after this time. |
| - State | Filter issues by state. Options: "All" (any state), "Closed", or "Open". Default is "Open". |
Output
The node outputs an array of JSON objects representing GitHub issues. Each object corresponds to one issue and contains fields as defined by the GitHub API, such as issue title, body, state, labels, assignees, creation and update timestamps, and more.
No binary data output is produced by this operation.
Dependencies
- Requires a valid GitHub API authentication credential, either an access token or OAuth2 credentials.
- The node uses GitHub's REST API endpoint
https://api.github.comto fetch issues. - For repository and user selection, it depends on internal methods to list available users and repositories.
Troubleshooting
- Authentication errors: Ensure that the provided access token or OAuth2 credentials have sufficient permissions to read repository issues.
- Invalid repository or owner: Verify that the repository owner and name are correct and accessible with the given credentials.
- Rate limiting: GitHub API enforces rate limits; if exceeded, requests will fail. Consider using authenticated requests to increase limits.
- Pagination issues: When "Return All" is enabled, the node paginates through results. Network interruptions or API changes might cause incomplete data retrieval.
- Invalid filter values: Ensure date formats and state values conform to expected formats to avoid request errors.