# Operators + GitHub: pull requests waiting for your review

Source: https://founder.nexxascreen.com/integrations/github  
Updated: 2026-11-20  
Publisher: Sentient AI Inc

> Coming soon. Operators reads GitHub and shows the pull requests asking for your review, the issues assigned to you whose milestone has a due date, and your pull requests merged today, next to the rest of your companies. GitHub has no read-only permission for private repositories, so it asks for more than Operators uses. Operators only ever reads.

Status: Coming soon.

| On your board | From GitHub |
|---|---|
| Waiting on you | Pull requests asking for your review |
| Due (shown when the day comes) | Issues assigned to you whose milestone has a due date |
| Done today | Your pull requests merged today |

## Why connect GitHub to Operators?

For a technical founder, "waiting on you" usually means a pull request. When the companies you run each have their own organisation and repositories, review requests are spread across separate notification lists. Operators lists them on one board, labelled by company, so the one blocking a release is the one you open first.

## Can each organisation go to its own company?

Yes. One GitHub account often belongs to several organisations, one per venture. On GitHub's page in Tools, under Where items go, choose a company for each organisation. Work from an organisation with no choice goes to the connection's default company, or waits in Unsorted. Operators files by organisation, not by repository, and it never reads code.

## What we keep from GitHub

- Pull request or issue title
- Organisation name (to choose the company)
- Milestone due date
- Link

Never message text, email bodies or file contents.

## Limits and permissions

- GitHub has no read-only permission for private repositories, so it asks for its repo permission, which also allows changes. We only ever read.
- Organisations with SAML single sign-on need you to authorise the app for them on GitHub.

## Steps

1. **Choose the company.** On your board, open Tools, pick GitHub and choose which company this account's work belongs to.
2. **Sign in to GitHub.** Approve the app on GitHub. If an organisation uses single sign-on, authorise the app for it too.
3. **Review what is waiting.** Pull requests asking for your review appear under Waiting on you, with a link that opens each one on GitHub.

## Questions

### Why does GitHub ask for permission to change my repositories?

GitHub offers no read-only permission that covers private repositories, so the sign-in asks for its repository permission, which also allows changes. Operators only sends read requests and never changes anything.

### My organisation uses single sign-on. Will it work?

Yes, once you authorise the app for that organisation on GitHub. GitHub shows the button on its own settings page for organisations that use SAML single sign-on.

### Which issues show up?

Issues assigned to you whose milestone has a due date. Issues without a milestone date are not brought in, so the board never invents a deadline.
