GitHub setup
Install the Tempo GitHub App, choose the repositories Tempo can access, and select which of those repositories to track. Tempo discovers accessible repositories and keeps subsequent syncs incremental.
- Install through GitHub’s app authorization flow.
- Limit access to the repositories you choose.
- Start with historical metadata, then keep metrics current.
- Add Tempo CLI only when file-level AI attribution is wanted.
Metadata synchronized from GitHub
Tempo normalizes GitHub objects into a consistent delivery model. Detailed pull-request statistics are fetched when needed, and review and event timelines support stage-level metrics.
- Repositories, default branches, and language breakdowns.
- Commits, authors, timestamps, messages, and change statistics.
- Pull requests, reviews, reviewers, comments, and lifecycle events.
- Deployments, environments, outcomes, and linked pull requests.
Metrics produced from GitHub
GitHub timestamps, lifecycle events, change statistics, and deployment records support the following calculations.
- PR cycle, pickup, review, draft, and rework time.
- Blocked, long-lived, abandoned, large, and no-review pull requests.
- Deployment frequency and lead time to production.
- Review load, collaboration patterns, and AI-assisted work.
Data boundaries
Standard metric calculations use titles, timestamps, identities, states, and numerical change statistics. GitHub API responses may contain additional fields; metric normalization retains the fields needed for those calculations.
Tempo CLI sends attribution metadata rather than source contents, diffs, prompts, or transcripts. Entire Checkpoints is a separate path: it stores prompts, context, and compact transcripts when present and within size limits. Those texts can contain code. The full event stream remains a Git reference and is not downloaded.