Integrations
Operators + GitHub: pull requests waiting for your review
Updated 1 min read By Operators team
What you will see from GitHub
| 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.
How to connect GitHub
-
Choose the company
On your board, open Tools, pick GitHub and choose which company this account's work belongs to.
-
Sign in to GitHub
Approve the app on GitHub. If an organisation uses single sign-on, authorise the app for it too.
-
Review what is waiting
Pull requests asking for your review appear under Waiting on you, with a link that opens each one on GitHub.
What we keep from GitHub, and what we never keep
We keep, for each item
- Pull request or issue title
- Organisation name (to choose the company)
- Milestone due date
- Link
We never keep
- The full text of messages, emails, meeting notes or files
- A copy for training any AI model
- 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.
The full list for every tool is on the security page. Connecting a client's GitHub? Send their IT team this page.
GitHub is coming soon
Tell me when
Questions people ask
- 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.
Related
- Integrations Operators + Linear: issues waiting on you, every company Connect Linear to Operators to see issues in review, issues due and work your teams finished today, with each workspace filed under its own company. 2 min read
- Articles Read-only by default, a sane rule for connecting tools Why every new connection between your tools, apps and AI assistants should start read only, when to allow changes, and what to check before approving. 5 min read
- Articles The waiting-on-you list every operator should keep Why a list of what is blocked on you matters more than a to-do list when you run several companies, what belongs on it, and how to keep it short. 5 min read