Dash0 acquires Polar Signals
Connect your GitHub repositories to unlock PR cycle time, pipeline flow, and assisted vs. non-assisted developer metrics.
Coding agents tell you what they cost and how widely they are used. They cannot tell you whether the work actually ships. That signal lives in GitHub: when a pull request opens, how long it waits for review, how often it comes back, and when it finally merges.
Connecting GitHub gives Dash0 the delivery half of the picture. Pair it with at least one coding agent and Dash0 can compare assisted and non-assisted work side by side, instead of reporting token spend that nothing ties to an outcome.
This is the delivery telemetry connection for AI SDLC Insights. If you are looking to give Agent0 access to your repositories for AI-assisted investigations, or to send GitHub Actions telemetry to Dash0, see the GitHub service integration instead.
Dash0 reads delivery activity through a GitHub app installed on your organization. There is nothing to deploy and no workflow to add: once the app is installed and pointed at a set of repositories, GitHub sends pull request and workflow events to Dash0, and the AI SDLC Insights section starts reporting on them.
GitHub asks which repositories the app may access during installation. Grant access to the repositories you want reported on — either all of them, or a selected list you can extend later from the installation's page on GitHub.
Dash0 reports on nothing until this is set. An installation with no repositories selected is the most common reason the insights pages stay empty after a successful install.
Back in Dash0, open the installation in Settings → Integrations and choose the dataset the GitHub data belongs to. Pick the same dataset your coding agents send to, otherwise the two halves cannot be correlated.
If a widget still says GitHub is not set up, it names the missing piece — no repositories, no dataset, or a suspended installation — and links to the page that fixes it.