Skip to content

Connect GitHub to Infograph

What it brings in: issues, pull requests, commits, comments, reviews and 4 more.

Connect GitHub 4 steps to set up

What you need

  • A GitHub account with access to the repositories you want to analyse.
  • To add an organisation's repositories, you need to be an owner of it, or an owner must approve your request.

Steps

  1. Open GitHub in Infograph

    Open GitHub in Infograph and press Continue to GitHub. A GitHub window opens. Sign in if it asks you to.

    Continue to GitHub

  2. Choose where to install Infograph

    Infograph connects as a GitHub App. Pick your personal account or the organisation that owns the repositories.

  3. Choose the repositories

    Choose All repositories, or Only select repositories and pick them from the list. Infograph reads only the repositories you choose here. Confirm the install.

  4. Choose what to sync

    Each repository has its own issues, pull requests, reviews, commits and releases, and Repositories lists them all. Commits come from each repository's default branch. Pick what you want and Infograph starts loading it.

Or connect with an access token

  1. Create a fine-grained token

    In GitHub, open Settings, Developer settings, Personal access tokens, Fine-grained tokens, and click Generate new token. Name it Infograph and pick an expiry.

  2. Choose the owner and repositories

    Under Resource owner, pick your account or the organisation that owns the repositories. Under Repository access, choose All repositories or Only select repositories. An organisation may need an owner to approve the token before it works.

  3. Give it read access

    Under Repository permissions, set Read-only on Issues, Pull requests and Contents. Metadata is read-only already. Generate the token and copy it: it starts github_pat_, and GitHub shows it only once.

  4. Paste it in Infograph

    Open GitHub in Infograph, choose Use an access token instead, paste the token into Access token and press Connect. Pick what you want and Infograph starts loading it.

    Connect

What it syncs

Each becomes a table in Infolake that you can chart, report on or ask about. You choose which to sync.

Issuesissues

Every issue in the repositories you choose, with its state, labels, assignees and when it was opened and closed. The base for backlog, bug and response-time dashboards.

Ask: “How many bugs did we open and close each week this quarter?”

Pull requestspull_requests

Every pull request, with its author, state, branches and when it was opened, merged or closed. Shows how fast work moves from first commit to shipped.

Ask: “What is our median time from opening a pull request to merging it?”

Commitscommits

The commits on each repository's default branch, with author, date and message. Shows who is shipping and how often.

Ask: “Which repositories had the most commits last month, and from whom?”

Commentscomments

The conversation on issues and pull requests, with who wrote each comment and when. Shows where discussion piles up.

Ask: “Which issues have the longest discussions but are still open?”

Reviewsreviews

Each review left on a pull request, with the reviewer, their verdict (approved, changes requested or commented) and when. Shows who reviews and how quickly.

Ask: “Who reviews the most pull requests, and how long do authors wait for a first review?”

Show all 9 tables
Pull request sizepull_request_stats

The size of each pull request, lines added and removed, files changed, commits and review comments. Shows whether smaller changes ship faster.

Ask: “Do large pull requests take longer to merge than small ones?”

Review commentsreview_comments

Line-by-line comments left on code during review, with who wrote them and where. Shows how much back and forth a change needs.

Ask: “Which repositories get the most review comments per pull request?”

Releasesreleases

Each published release, and drafts, with its tag, name and publish date. A timeline of what shipped when.

Ask: “How often have we released each product this year?”

Repositoriesrepositories

The repositories Infograph can read, with their language, visibility, stars, forks, open issues and when they were last pushed to. Ties every other table to the project it belongs to.

Ask: “Which of our repositories are most active, and which have gone quiet?”

Troubleshooting

Each entry is the message Infograph shows when a connection fails. Open it for the fix.

Those credentials were not accepted.

GitHub did not accept the token. Check you copied all of it, from github_pat_ to the end. A token that expired, was deleted, or was not yet approved by an organisation owner stops working: check it under Settings, Developer settings, Personal access tokens, create a new one if needed, then open the connection in Infograph, choose Edit configuration and paste it.

Access was not allowed, so nothing was connected. Connect again and choose Allow.

The sign-in was answered with Cancel or Deny, so nothing was connected and Infograph holds no access. Press Connect again and choose Allow. Infograph uses the access only to read and sync your data.

Your account cannot read this data. Ask an admin of the account for access, then connect again.

GitHub refused a request for this data. Check Infograph still has the repository in its Repository access. For your own account, go to Settings, Applications, Installed GitHub Apps and press Configure next to Infograph. For an organisation, an owner opens the organisation's Settings, then GitHub Apps under Third-party Access. Add the repository, press Save and connect again.

Infograph's access was removed or has expired. Re-authenticate to resume syncing.

GitHub no longer accepts Infograph's access. The app may have been uninstalled or suspended, which you can check in Settings, Applications, Installed GitHub Apps, or in the organisation's settings under GitHub Apps. Press Re-authenticate. If the app was uninstalled, install it again on the same account and choose the same repositories. If syncs keep failing after that, check Infograph still has access to the repositories you sync.

Common problems

These happen in GitHub itself, where Infograph cannot see them.

The organisation is waiting for an owner

If you are not an owner of the organisation, GitHub sends your request to its owners instead of installing Infograph. Nothing appears until an owner approves it. Ask them to, then connect again.

A repository is missing

Infograph only sees the repositories the app may read. Press Configure next to Infograph under Installed GitHub Apps, add the repository under Repository access and press Save. Then open the connection in Infograph and press Re-discover streams. Archived repositories are skipped.