Integrations / GitHub

GitHub

GitHub code collaboration and version control platform

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A GitHub organization or personal account you can install apps on.

Owner or app-manager on the organization. Members cannot complete the install.

Vendor setup

Get the credential

Open the install link

In Telara, open Settings → Integrations → GitHub and click the GitHub App install link from your administrator. This is Telara’s app — you do not create a GitHub App.

Choose the account and repositories

GitHub asks which account to install on. Pick the organization (or your user). Then choose All repositories, or Select repositories and tick the ones Telara should see.

Click Install and return

GitHub redirects you back to Telara. Finish Connect under Settings → Integrations if it is not already marked connected.

Permissions Telara requests

repo
OAuth 2.0
read:org
OAuth 2.0
read:user
OAuth 2.0
user:email
OAuth 2.0
workflow
OAuth 2.0
security_events
OAuth 2.0
audit_log
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Personal access token

GitHub Personal Access Token (classic or fine-grained)

In Telara, open Settings → Integrations, choose this connector, and paste the token into the field Telara shows.

Fields Telara asks for

Access token

GitHub App

GitHub App installation token

Install Telara’s GitHub App using the installation link from your administrator, then finish Connect under Settings → Integrations.

Fields Telara asks for

App ID
Installation ID
Private key

Knowledge

What gets indexed

Resource	Coverage
Repositories	Partial — not every record the vendor holds is synced
Pull requests	Partial — not every record the vendor holds is synced
Commits	Partial — not every record the vendor holds is synced
Releases	Partial — not every record the vendor holds is synced
Issues	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Repositories	Up to 1 day	Removed records disappear on the next full sync
Pull requests	Up to 1 day	Removed records disappear on the next full sync
Commits	Up to 1 day	Removed records disappear on the next full sync
Releases	Up to 1 day	Removed records disappear on the next full sync
Issues	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Repositories, Pull requests, Commits, Releases, Issues.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Repository access is whatever you granted at install time. Unchecking a repository in GitHub drops it from Telara on the next sync.

Fine-grained personal tokens are a fallback for automation, not the default path. Prefer the App.