Lesson 06 · GitHub platform · insights
Insights & Traffic
The Insights tab turns repo activity into charts — who's contributing, what's changing, and (for a public repo) who's actually visiting.
Every repo tab you've used so far — Issues, Actions, Projects, Security — is where work happens. Insights is different: it's read-only, no actions to take, just charts answering "what's been going on in this repo."
The Insights sub-pages
Pulse A weekly/monthly digest: commits, merged PRs, opened/closed issues, active contributors. The "what happened recently" summary.
Contributors Commit count per person, over time, as a graph. Who's actually pushing code, and when activity picked up or dropped.
Commits / Code frequency Commit volume and lines added/deleted, plotted over the repo's whole history. Spot when a big refactor happened.
Network A visual branch graph across all forks of the repo, not just yours — see how forks diverged and where they'd merge back.
Traffic Views and clones, last 14 days. The only chart with visitors who never touched the code.
Traffic is the odd one out
Pulse, Contributors, Commits, Network — all derived from git history, which is public on a public repo regardless of who's watching. Traffic is different: it counts people who looked, not people who committed.
| Metric | Counts | Window |
|---|
| Views | Page loads of any page in the repo (code, issues, PRs, etc.) | Last 14 days, daily |
| Unique visitors | Distinct people behind those views | Last 14 days, daily |
| Clones | git clone / git fetch operations | Last 14 days, daily |
| Referring sites | Where view traffic came from (Google, a tweet, another site) | Top 10, rolling |
Two catches worth knowing before you rely on it
Traffic data only covers the last 14 days — nothing older is retained, so it's for spotting recent trends, not a historical record. And it's visible only to people with push access to the repo, even on a public repo — visitors can't see their own view counted back at them, and you can't see traffic on a repo you don't have write access to.
Third catch — plan, not permission
On
GitHub Free, six graphs —
Pulse, Contributors, Traffic, Commits, Code frequency, Network — only render for
public repos, full stop. Push access doesn't override it. Make the repo private on Free and those six tabs vanish from the sidebar entirely; what's left is
Dependency graph, Forks, and (if Actions is enabled)
Actions usage metrics and
Actions performance metrics. This workspace's repo (
stianbranden/learning) is private, so that's exactly what you'll see — it's the plan tier, not a bug or a missing permission. Pro/Team/Enterprise Cloud unlocks all six on private repos too. Source:
GitHub Docs — About repository graphs.
What these are for
None of this is actionable the way an Issue or a failing Action is — there's no button to click in response to a chart. It's context: Contributors tells you if a project is a one-person effort or has real team velocity. Traffic tells you if anyone's actually finding your Pages site or README, which matters if you're writing documentation or an OSS project hoping for outside contributors. For this workspace specifically, Traffic is the only signal for whether the Pages site you published in lesson 4 gets visited by anyone but you.
Your win — read this repo's own signals (private-repo edition)
Because stianbranden/learning is private on Free, Pulse/Contributors/Traffic aren't reachable here — use the sub-pages that are open:
- Open Dependency graph — see what the repo depends on (or confirm it's empty, since this workspace has no build).
- Open Forks — confirm it's zero; this is a solo practice repo.
- From the repo's Insights tab, click Actions usage metrics in the sidebar — see which workflows have run and how much compute they've used.
If you ever make this repo public (or upgrade the plan), Pulse/Contributors/Traffic/Commits/Code frequency/Network open up immediately — same repo, same history, just gated by that one setting.
Go deeper
Primary source — read this one: GitHub Docs — Viewing traffic to a repository. Covers views, clones, referring sites, and the 14-day / access-level caveats in full.