Skip to main content
Early access. Connecting GitHub today mirrors your repositories into Zudo and nothing else. Linking pull requests to requests, and closing a request when the work ships, are still being built. This page says exactly what works now. Ask your Zudo contact to turn the integration on for your organization.
Zudo connects to GitHub through a GitHub App you install on your own account or organization. You choose which repositories it can see, on GitHub’s own install screen, and the app only ever reads.

​
Connect

1

Start from Zudo

Go to Settings → Connections, click Add Connection, and choose GitHub. Only owners and admins can add a connection.
2

Pick the account

Zudo sends you to GitHub to install the app. Choose the personal account or organization whose repositories you want to connect. If you are not an owner of that organization, GitHub asks an owner to approve the install instead, and nothing is connected until they do.
3

Choose the repositories

Grant access to All repositories or Only select repositories. This is the access boundary, and it stays under your control on GitHub — Zudo cannot widen it.
4

Come back to Zudo

GitHub returns you to Settings → Connections. The connection appears with the repositories it can see.
You can connect more than one GitHub account to the same Zudo organization. A GitHub App is installed per account, so a company with repositories under two GitHub organizations needs one installation for each, and both appear as separate connections.

​
What Zudo reads

The app requests read-only access to five things, and nothing else: Zudo never writes to GitHub. It posts no comments, sets no labels, and creates no status checks. It has no permission to do any of those.

​
Watching repositories

Two different things decide whether Zudo looks at a repository. Access is set on GitHub, under the installation. It is what the app can see at all. Change it with Manage access on GitHub on the connection card. Watch is set in Zudo, per repository. Every repository you grant is watched by default, because you already chose them on the install screen. Turning Watch off stops Zudo looking at that repository without changing anything on GitHub — useful for a repository that is noisy or irrelevant to customer work. If the list in Zudo disagrees with what you granted on GitHub, press Refresh on the connection card to rebuild it.

​
What works today

  • Installing the app and connecting one or more GitHub accounts
  • Listing the repositories the installation can see
  • Choosing which of those Zudo watches
  • Keeping that list current when you add or remove repository access on GitHub

​
What does not work yet

  • Pull requests are not linked to requests
  • Requests do not change state when a pull request merges or deploys
  • Nothing about GitHub appears on a request, an account, or in a report
These are being built in order. Until they land, the connection is safe to set up early: Zudo starts collecting nothing it would need to backfill later.

​
Disconnecting

Deleting the connection in Zudo removes the repository list and stops Zudo reading anything. It does not uninstall the app from GitHub. That is deliberate — Zudo should not be able to change your GitHub account’s settings. To revoke access fully, remove the Zudo app from your GitHub account or organization under Settings → Applications → Installed GitHub Apps. If you uninstall the app on GitHub without deleting the connection in Zudo, the connection is disabled automatically and its history is kept.

​
Troubleshooting

  • “That installation does not belong to your GitHub account” — you were signed in to a different GitHub account than the one that owns the installation. Sign in as the right account and try again.
  • “That installation link has expired” — the install link is valid for ten minutes. Start again from Add Connection.
  • The repository list looks wrong — press Refresh on the connection card. If a repository is still missing, check it is granted under Manage access on GitHub.
  • Nothing happened after approving — if you are not an owner of the GitHub organization, your request goes to an owner for approval. The connection appears once they approve it, and you will need to complete the install again.