Coding time from the VS Code extension tells you how long you spent in the editor. But it does not tell you what you shipped. GitHub activity fills that gap — commits pushed, pull requests opened and merged, code reviews completed.
What Gets Synced
When you connect GitHub via OAuth, xeve syncs three types of activity:
- Commits — every commit you authored across all accessible repos, with message, repo name, additions/deletions, and timestamp
- Pull Requests — PRs you opened, with title, repo, state (open/merged/closed), and review status
- Reviews — code reviews you submitted on other people's PRs, with the review state (approved, changes requested, commented)
The sync runs via a Supabase edge function (github-sync) that paginates through the GitHub Events API. It handles rate limiting, deduplication, and token refresh automatically. Initial sync grabs the last 90 days of activity. Subsequent syncs are incremental — only new events since the last sync.
The GitHub Dashboard Page
The GitHub page in the dashboard shows:
- Daily contribution chart — a bar chart of commits per day, colored by the dominant repo that day
- Total stats — commits, PRs opened, PRs merged, reviews completed for the selected period
- Lines changed — total additions and deletions, which gives a rough (if imperfect) measure of output volume
- Active repos — sorted by commit count, with language tags
- Recent activity feed — a chronological list of commits, PRs, and reviews with timestamps and repo context
GitHub × Coding Time
The most interesting view is implicit: the dashboard's Overview page shows both coding time (from VS Code / Claude Code) and GitHub commits on the same daily timeline. You can see whether your coding sessions actually resulted in commits, or whether you spent 6 hours in the editor and pushed nothing.
The correlation engine also uses GitHub data. It computes relationships between commits-per-day and metrics like sleep, steps, focus time, and music listening. In my data, there is a moderate positive correlation (r=0.45) between coding hours and commits — which means about half the time, more time in the editor does translate to more shipped code. The other half is debugging, reading, and yak shaving.
Org-Level GitHub
For organizations, GitHub activity is even more powerful. The CTO dashboard aggregates commits, PRs, and reviews across all team members. You can see which repos are most active, which team members are shipping, and where code reviews are bottlenecked. The Developer Table shows each engineer's commit count, PR velocity, and review turnaround time.
This is not surveillance — it is visibility. The same data is available on GitHub itself, but scattered across repos, profiles, and notification emails. xeve puts it in one view.