Skip to main content

GitHub integration

Connect GitHub to Leanmote so commits, PRs, and reviews populate every dashboard.

The GitHub integration is one of Leanmote's two foundational data sources (the other is your planning tool). It powers the DORA metrics and the pull-request metrics. Flow metrics do not come from GitHub — Cycle Time, Throughput, WIP, Flow Efficiency, Waiting Time and Time to Market all read from your task-management tool, so connecting GitHub alone leaves them empty. The Team Collaboration Network draws on GitHub together with your chat, task and calendar integrations.


​

What Leanmote pulls from GitHub


​

  • The repositories you give Leanmote access to — with the GitHub App, the ones you choose in GitHub.

  • Commits, including author and timestamp metadata.

  • Pull requests, including open/merge/close timestamps and labels.

  • Pull-request reviews and review comments.

  • Pull-request comments and review threads.

  • Deployments — environment, whether GitHub marks it as production, state (success / failure / error), ref, commit, and timestamps.


​

Deployment data and DORA


​

Deployments recorded through GitHub's Deployments API are captured continuously, whether or not you use them for DORA — by default DORA counts merged pull requests as deployments instead. To have Deployment Frequency and Change Failure Rate count the deployments themselves, the organization owner chooses GitHub deployments in Settings → Organization Settings → Tabs → Metrics, under Where deployments are counted. Choosing it backfills up to a year of deployment history automatically.


​

Two shapes of deployment are supported:


​

  • GitHub deployments — anything recorded through GitHub's Deployments API, which is what GitHub Actions environments and most CD tools create. Nothing to configure.

  • Deploy check runs — for pipelines that deploy without creating deployment objects, Leanmote can treat a named production check run on your release tags as the deployment. Ask your Leanmote contact to configure the check name for your organization. Capture starts when the setting is turned on, and the backfill brings in the earlier history.


​

See Deployment Frequency and Change Failure Rate for how each metric counts them.


​

Connect GitHub


​

Leanmote connects to GitHub through the Leanmote GitHub App. It is installed on your GitHub organization rather than on someone's personal account, so it keeps working when people join or leave, and it reads with its own GitHub quota instead of the personal quota of whoever connected it.


​

  1. Open Administration → Integrations (or the integrations step of the guided setup).

  2. Find GitHub under Code & Git and click Connect.

  3. GitHub opens the installation page of the Leanmote app. Pick the GitHub organization that owns your repositories.

  4. Choose All repositories or Only select repositories. Leanmote reads exactly what you choose here, and you can change it later in GitHub.

  5. Click Install & Authorize. GitHub sends you back to Leanmote and the import starts.


​

  • Not an owner of the GitHub organization? If you're an admin of the repositories, GitHub usually lets you install it on them yourself. Otherwise you can request it, and GitHub emails your request to the organization's owners. When one of them approves it, GitHub connects on its own; you don't need to come back.

  • Connected once, for everyone. Once the App is installed, GitHub shows as connected for everyone in your Leanmote organization; nobody else needs to install it.

  • Changing the repositories. In GitHub, open your organization's Settings → GitHub Apps, find Leanmote and click Configure. Leanmote picks up the change on its own and starts reading the repositories you added.


​

Connections made with OAuth (previous method)


​

Before the GitHub App, each person connected GitHub with their own account through OAuth: Connect, sign in to GitHub, authorize Leanmote, and choose the repositories in Leanmote. Those connections keep working. Leanmote keeps reading the repositories on them, with the personal GitHub quota of whoever connected, until you move them to the App. New connections always use the App.


​

Move from OAuth to the GitHub App


​

  1. Open Administration → Integrations and click Manage on the GitHub card.

  2. At the bottom of the window, click Switch to the GitHub App. You only see it while your organization doesn't have the App yet.

  3. In GitHub, pick the GitHub organization that owns your repositories and choose All repositories, or at least the ones Leanmote reads today. Click Install & Authorize. If you aren't an owner of that organization, click Request instead: GitHub emails the owners, and once one of them approves it, GitHub connects on its own.

  4. Back in Leanmote, the repositories you already track move to the App with their history; nothing is imported again. Repositories the App doesn't cover are switched off: to measure them, install the App on their GitHub account too, and switch them on in Manage.

  5. From then on, GitHub shows as connected for everyone. Anyone who wants to remove their personal OAuth connection can click Disconnect GitHub in Manage: it removes only their OAuth, and the App keeps reading.


​

Permissions requested


​

The Leanmote GitHub App asks only for read access, and it can't write to your repositories:


​

  • Metadata — repository names and basic details.

  • Contents — commits, branches and tags.

  • Pull requests — pull requests, reviews and review comments.

  • Issues — comments on pull requests, which GitHub keeps as issue comments.

  • Checks — check runs, including deploy check runs.

  • Deployments — deployments and their states.


​

Connections made with OAuth, before the App, were granted these scopes:


​

  • repo — required to read commits, pull requests, reviews, and deployments from private repositories. GitHub does not offer a read-only equivalent for private repos: the repo scope grants both read and write access. Leanmote uses it strictly for read operations and never writes back to your repositories.

  • read:org — read your organization's membership and team list, used to map GitHub identities to Leanmote teams.

  • user:email — read your user profile email so we can match GitHub authors to Leanmote teammates.


​

If your security team needs to verify Leanmote's behavior, the GitHub audit log is the source of truth — every API call is logged on your side and you'll see only read operations.


​

Sync schedule


​

  • Initial import: the last year of history of each repository.

  • Incremental sync: scheduled refreshes throughout the day read what changed since the previous one.


​

Disconnecting GitHub


​

  • Disconnect GitHub, in Manage, removes your personal OAuth connection if you have one. The GitHub App stays installed and keeps reading.

  • If you installed the App and have no OAuth connection of your own, Disconnect GitHub uninstalls the App from your GitHub organization, and Leanmote stops reading through it for your whole organization. To connect again, the App has to be installed again.

  • To remove the App altogether, uninstall it in GitHub: Settings → GitHub Apps → Leanmote → Configure → Uninstall. Leanmote notices and stops reading through it.


​

Common issues


​

  • Some repos missing — check that they're among the repositories the App can read (Settings → GitHub Apps → Leanmote → Configure in GitHub). On an OAuth connection, re-open the integration to add or remove repos.

  • Installation waiting for approval — GitHub emailed your request to the owners of your GitHub organization, and one of them still has to approve it. Once they do, GitHub connects on its own. If it still isn't connected after they approved it, click Connect again.

  • Stopped after someone left — an OAuth connection belongs to the person who made it and stops working when they lose access. Switch to the GitHub App, which belongs to the organization.

  • Bot commits inflating metrics — exclude bot accounts in your team mapping.

  • No deployments showing — check that your pipeline creates GitHub deployments (or a deploy check run) and reports their final state. Deployments to environments GitHub doesn't mark as production are only counted when your organization marks no environment as production at all.


​

Related articles


​

  • Integrations overview

  • Connect your first integrations

  • Sync isn't completing

  • Integration shows disconnected

Did this answer your question?