GitHub
An end user's commits, pull requests, reviews and issues on GitHub, in their memory.
GitHub's sign-in reads the connected person's own activity and what they are involved in: what they pushed and opened, the reviews and comments on their pull requests, their notifications and the runs that failed.
Connect it
In the console, open Connectors, pick GitHub, check whose memory it feeds, and Continue to GitHub. Sign in on github.com and approve; you come back connected, and the last 90 days start arriving within a few minutes. See Connectors for what happens to what it reads.
What it reads
| Source | What it holds | Read |
|---|---|---|
| Events | Your own activity - commits, branches, issues, pull requests, reviews, releases | every minute |
| Notifications | Threads you are subscribed to - mentions, review requests, assignments, with what was said | every minute |
| Pull activity | Reviews and comments others leave on pull requests you opened, review or follow | every 5 minutes |
| Workflow failures | Workflow runs you started that failed or were cancelled | every 5 minutes |
| Items | Issues and pull requests you are involved in, as they stand now, with others' comments on issues | every 5 minutes |
Good to know
- An organisation that restricts OAuth apps has to approve this one: the person can request it on GitHub's consent screen, and an owner approves it under the organisation's Settings → Third-party access. Until then, that organisation's repositories are not read.
- Workflow failures are runs the person started that failed or were cancelled - the ones they would want to know about.