Muon + GitHub
Connect GitHub to Muon so product changes can be investigated with real release and deployment context — the release that likely caused a metric to move is right there on the timeline.
What does the Muon GitHub integration do?
The GitHub integration brings releases, tags and deployment events onto the Muon timeline, so Findings can be correlated with the release that likely caused them.
When a metric moves, you no longer have to remember what shipped that day. Muon already has the deploy on the timeline — statistics detect the change first, and the matching release is offered as a likely related signal, not a guess.
Release and deploy signals, on the timeline.
Muon reads a focused set of engineering events — enough to place a change in time and link back to the source — never your source code.
Release and deploy events
Published releases, version tags and deployment events across your environments, each landing on the Muon timeline at the moment it happened.
Accurate timestamps
Every event carries the exact time it occurred, so Muon can line it up against the moment a metric started to move.
Related metadata
Repository, environment, version tag, author and release notes — the context that tells you which change this actually was.
Links back to source
Each timeline event links straight back to the GitHub release, tag or deployment, so a click takes you to the exact change.
From "a metric moved" to "which release moved it."
Once GitHub events share a timeline with your product metrics, investigation stops being archaeology.
Timeline events
Releases and deploys appear as first-class markers alongside pageviews, conversions and browser health signals.
Correlation with product metrics
Muon scores whether a change in a metric lines up in time with a release — surfaced with confidence and impact, not certainty.
Investigation context
When you open a Finding, the nearby releases are already attached, so the first question — "did we ship something?" — is answered.
Insight summaries
Muon Pro can write a plain-language summary that names the likely-related release, so the change is legible without opening a dashboard.
What a GitHub-correlated Finding looks like.
Correlation is not causation — Muon surfaces the release as a related signal with confidence and impact so a human decides what is likely connected.
Five steps to GitHub on your timeline.
The official GitHub integration is part of Muon Pro. On Community, the same events can flow in through the open connector API.
Open Settings → Integrations
Head to the Integrations panel in your Muon project settings.
Choose GitHub
Select GitHub from the official integration catalogue.
Authorize access
Grant read access to release, tag and deployment metadata via GitHub OAuth or an app installation.
Select repositories and environments
Map the repositories and deployment environments to the Muon projects where their events belong.
Start receiving timeline events
Releases, tags and deploys flow onto the timeline and become available for Findings.
Questions, answered directly.
What does the Muon GitHub integration do?
Is the GitHub integration free?
Does connecting GitHub give Muon access to my source code?
Put every release next to the metrics it moved.
Official integrations like GitHub are part of Muon Pro — and a community connector API lets any team push the same events on Community.