GitHub Issues
GitHub Issues reads the issues of a GitHub repository and returns the text of each one along with its details: title, author, state, labels, assignee and link. It also returns the repository’s pull requests, marked as such.
When to use it
- Prepare a weekly summary of a product’s open issues.
- Have an agent sort new issues by urgency.
- Look for similar issues before opening a new one.
Configuration
| Field | What it does |
|---|---|
| Access Token | Your GitHub personal access token. Needed to read private repositories. |
| Repository | The repository, in the format owner/repository, for example mycompany/website. |
| Labels | Reads only the issues that have these labels. Leave it empty to read them all. |
| State | Which issues are read according to their state: open, closed or all. Default: all. |
Output
The Data output returns one item per issue or pull request, with its text and its details: title, link, number, author, creation date, number of comments, state, labels, assignee and milestone, and whether it is a pull request.
Example
A product team wants to review the pending bugs every Monday:
- Add GitHub Issues, enter your token and the product’s repository.
- In Labels, enter
bugand, in State, pick open. - Connect Data to an agent that groups the bugs by topic and points out the oldest ones.
- Send the summary to the team’s channel.
Good practices
- Use a token with read-only access to the repositories you need.
- Filter by label and state so you don’t read the repository’s whole history.