Your Git history already knows how your team works.
GitObs reads commits, contributors and pull requests from GitHub and shows where engineering time goes, who owns which code, and where pull requests wait.
Built from the data GitHub already has
No agents to install and no new process for the team. GitObs works from your commits, pull requests and contributors.
See where the work goes
Commit and line-change activity per repository, team and week, so a quarter of migration work or a week of firefighting shows up as what it was.
billing-service, last 7 days
- a3f9c1eMove invoice PDFs to a background job+214−96
- 9b02d7fFix flaky checkout test on CI+12−40
- e41c88aRetry GitHub webhook deliveries+58−7
- 1d7f6b2Remove legacy v1 billing endpoints+3−1,208
Know who knows what
Who changed which parts of the codebase, from commit authorship. Spot the areas that only one person has touched before that person goes on holiday.
| Directory | People | Top contributor share |
|---|---|---|
| services/billing/ | 1 | 91% |
| infra/terraform/ | 2 | 64% |
| web/checkout/ | 5 | 38% |
Follow pull requests from open to merged
How long each pull request stays open before it merges, per repository and author, so the ones that sit for days stand out.
web-app, merged this week
- #482Split checkout into stepsopen 1d 10h
- #479Bump Node to 22open 2h 15m
- #471Rewrite invoice exportopen 6d 4h
- #468Cache exchange ratesopen 11h 30m
Median time to merge: 11h 30m
How it works
- 1
Connect GitHub
Install the GitObs GitHub App on your organization and choose which repositories it can read.
- 2
Choose repositories
Pick the repositories that matter. GitObs backfills their full history: commits, contributors, pull requests and releases.
- 3
Read the picture
Dashboards update as new commits and pull requests land, per repository, per team and across the organization.
Start with your own repositories
Set-up takes a few minutes.