# Operators + GitHub: pull requests waiting for your review

Source: https://useoperators.tech/integrations/github  
Updated: 2026-11-20  
Publisher: Sentient AI Inc

> Operators reads GitHub and shows pull requests asking for your review, issues assigned to you with a milestone date, and your pull requests merged today. You connect with a read-only key you make in GitHub. GitHub's one-click sign-in, when it is offered, has no read-only permission for private repositories, so it asks for more than Operators uses.

Status: Ready.

| 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.

## Two ways to connect

- **Your own read-only key.** The key screen opens GitHub's page for a new fine-grained personal access token, filled in as "Operators (read only)" with read access to pull requests, issues and metadata and nothing else. Choose the organisation (or yourself) as its resource owner and which repositories it may see, generate it and paste it in, with a name for the connection such as the organisation's. A key reaches one organisation, so connect once per organisation; each can feed its own company. Some organisations ask an owner to approve new keys, and until then only public work shows up: if nothing shows up after connecting, ask an owner to approve the key, or create it under the organisation. GitHub ends keys on the date you chose, and Operators emails you three days before.
- **One click, when it is offered.** Approve the Operators app on GitHub. It asks for GitHub's repository permission, because that sign-in has no read-only choice for private repositories.

Both bring in the same pull requests and issues, and a pull request that two of your keys can see shows once. Disconnecting deletes the key on our side; delete it in GitHub's settings too if you no longer need it.

## 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

- Connect with your own read-only key, once for each organisation. We only ever read.
- When one-click sign-in is offered, it asks for GitHub's repo permission, which also allows changes: GitHub has no read-only permission for private repositories there (only an app each organisation installs can be read-only).
- When one-click sign-in is offered and an organisation uses SAML single sign-on, authorise the app for it 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. **Paste a key you make in GitHub.** Make a read-only key on the page the key screen opens and paste it in, once for each organisation. Where one-click sign-in is offered, you can use that instead.
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

### Does Operators need permission to change my repositories?

No. With your own key it can only read, because the key screen fills in read access to pull requests, issues and metadata and nothing else. GitHub's one-click sign-in, when it is offered, has no read-only permission for private repositories (only an app each organisation installs can be read-only), so it asks for its repository permission, which also allows changes. Either way, Operators only sends read requests and never changes anything.

### Can I connect GitHub with a read-only key?

Yes, and that is the way to connect. The key screen opens GitHub's page for a new fine-grained personal access token, already named and set to read pull requests, issues and metadata. Pick the organisation as its owner, generate it and paste it in. A key reaches one organisation, so connect once for each one, and give each connection a name so you can tell them apart.

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

Yes. With your own key, an owner of the organisation may have to approve the key first, and until then only public work shows up. When one-click sign-in is offered, authorise the app for that organisation on GitHub, which 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.
