Skip to main content
Connectors

Connecting GitHub

Install the SREDlog GitHub App, approve repositories, and bring read-only commit, pull-request and issue summaries into the relevant project.

ReviewedAugust 22, 2026

ForClient portal users and claim preparers

Find itClient portal → Connect; consultant Client → Collaboration

The GitHub connector helps you reference development history without manually exporting every commit. The client owns the authorization. The consultant maps the approved repositories and runs the sync after the client connects them.

Authorize approved repositories

  1. The client signs in to their SREDlog portal and opens Connect.
  2. Choose GitHub, start authorization, and install the SREDlog GitHub App.
  3. In GitHub, approve only the repositories the client wants to share. GitHub's installation selection is the access boundary, so there is no second repository-sharing step in SREDlog.
  4. The consultant opens the client's Collaboration tab, opens Repositories, maps each repository to a SREDlog project, sets the activity window, and chooses Save & sync.

What the connection can access

SREDlog retrieves commit messages, timestamps, authorship, pull-request activity, and issue activity from repositories approved in the GitHub App installation. It does not store source-code contents and cannot push, open pull requests, or change repository settings.

Disconnect or troubleshoot

Repository access is controlled by the GitHub App installation. If a repository is missing, the installation owner must add it in GitHub. The consultant can then reopen Repositories in Collaboration and sync again. Disconnecting stops future syncs without erasing evidence already retained in a claim.

See the GitHub setup steps and data boundary.

Was this helpful?

Tell us what was missing and we’ll improve this guide.

Send feedback