Integrations / GitHub PR Output Signals

GitHub PR Output Signals

GitHub pull-request output-signal ingestion for the AI Platform Spend Governance feature. Counts PRs merged/opened per user across an org's repos to power the spend-vs-output scatter (plan §11.7). NOT a spend source; data_kind=output_signals isolates it from cost-allocation pipelines.

OAuth 2.0

Spend

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A GitHub organization whose pull requests Telara should count.

Owner, or a user who can create a fine-grained token (or install the GitHub App) with repository read.

Vendor setup

Get the credential

Prefer the GitHub App already connected

If GitHub is already connected for indexing, you can often reuse that install. Otherwise open Settings → Integrations → GitHub PR Output Signals.

Or create a fine-grained token

On GitHub, click your avatar → Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token. Pick the organization. Grant the permissions this page lists from the catalog. Copy the token once.

Paste in Telara

Paste the token (or finish App install) and name the organization whose merged PRs should feed spend-vs-output. This connector is output signals, not GitHub spend.

Permissions Telara requests

repo
OAuth 2.0
read:org
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

GitHub OAuth App authorization-code connection for repository and pull-request reads. API-key/PAT and GitHub App connections remain available.

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.

API key

GitHub Personal Access Token (classic or fine-grained) with `repo` and `read:org` scopes, OR a GitHub App installation token with PR read permission on the target org. Reuses the existing GitHub credential type from `github.yaml` operationally.

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

Fields Telara asks for

API key

Spend

What gets measured

Resolution: Not published.

Attribution: Matched to people by directory ID.

How far back vendor history goes is not published uniformly for this connector.

prs_merged
count — Count of pull requests merged in the window, attributed to user.login. PRIMARY output signal for the spend-vs-output scatter (plan §11.7).
prs_opened
count — Count of pull requests seen on this sweep (state=closed sweep — for prs_opened we need a parallel state=all sweep; engine combines).
pr_review_comments
count — Sum of review-comment counts across merged PRs. Proxy for review burden and collaboration signal.
pr_total_comments
count — Sum of issue-style comments across merged PRs.
pr_loc_added
count — Lines added across merged PRs. Opt-in — only emitted when github_pr_signals_deep_metrics=true (costs one extra request per merged PR).
pr_loc_deleted
count — Lines deleted across merged PRs. Opt-in (see pr_loc_added).
pr_files_changed
count — Files changed across merged PRs. Opt-in (see pr_loc_added).

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

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.

This catalog entry does not declare extra semantic-search exclusions.

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

This is not a substitute for the GitHub indexing connector. Approving PRs here does not index issues and files.

Tokens that cannot list org repos produce a successful connect and zero PRs.