Get issues
Gets a list of issues from a GitHub repository.
Example 
This flow gets a list of issues from a GitHub repository. For each issue, comments are read and stored in a SQL Server table.
Properties
| Name | Required | Description |
|---|---|---|
| Title | No | The title of the action. |
| Authentication | No | Select an authentication token. |
| Repository owner | Yes | Select or enter the repository owner. |
| Repository name | Yes | Select or enter the repository name. |
| Number of pages to fetch | No | Limit the number of pages to fetch. |
| Issues per page | No | Set the number of issues per page (1-200). |
| Issues since | No | Set the start date to fetch issues from. |
| Additional options | No | The configuration dialog contains settings for Issue state (Open, Closed), Sort options and Text format for the result (Text / HTML / Raw). |
| Result variable name | No | Name of the variable containing the issues list. |
| Description | No | Additional notes or comments about the action or configuration. |
Limitations
GitHub limits the number of REST API requests that you can make within a specific amount of time.
You can make unauthenticated requests if you are only fetching public data. Unauthenticated requests are associated with the originating IP address, not with the user or application that made the request. The primary rate limit for unauthenticated requests is 60 requests per hour.
For authenticated users the rate limit is 5,000 requests per hour. If the installation is on a GitHub Enterprise Cloud organization, the installation has a rate limit of 15,000 requests per hour.
Authentication
Authentication is done with an authentication token. Click here for more on creating a token.
GitHub: Videos / Getting started
This section contains videos to help you get started quickly with GitHub integrations in your Flow automations.
Deploy Microsoft fabric data pipeline from GitHub
This video demonstrates how to deploy a Microsoft Fabric data pipeline from GitHub using Flow.