TempoConnect GitHub in three steps
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
The same GitHub metadata powers organization summaries and drill-downs for repositories, contributors, pull requests, commits, and deployments.
- 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.
Metadata only by design
Tempo uses titles, timestamps, identities, states, and numerical change statistics to calculate metrics. The application does not request source-code contents for those calculations.
Tempo CLI follows the same boundary: local analysis may inspect supported session data, but only structured attribution metadata is eligible to sync.