What GitObs shows you
GitObs syncs repository history from GitHub and organizes it around the questions engineering leads actually ask: where the work goes, who knows which code, and where pull requests wait.
Commit activity
Commits and line changes per repository, contributor and week, with the full history backfilled when a repository is connected.
- Activity over time, so a migration quarter or a week of firefighting shows up as what it was
- Lines added and removed alongside commit counts, so one large change isn’t hidden by many small ones
- Breakdowns by repository and by team
Contributors and ownership
Who changed which parts of the codebase, built from commit authorship rather than a CODEOWNERS file someone forgot to update.
- Contributor profiles with the repositories and languages they work in
- Areas of the codebase where one person made most of the changes
Pull request flow
How long each pull request stays open before it merges, per repository and author, so the ones that sit for days stand out.
Repository health
- Language mix per repository
- Releases and the commits between them
- Stars over time for public repositories
Organizations and teams
Group repositories and people into organizations and teams, invite colleagues, and give each person a role that decides what they can see and change.
Getting access
GitObs is no longer opening new accounts. The team now builds AgentsTrack, which does the same kind of work for coding agents. Read what changed.