Linking Codecov (Sentry) as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Codecov (Sentry) connector syncs repos, branches, commits, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Codecov API token to automatically pull your code coverage data.
You can generate a personal API token under Settings → Access in your Codecov account. The token mirrors your own permissions on the git provider, so it can read every repository you can.
By default all of the owner's active repositories are synced; enter a comma-separated list of repository names to limit the import.
You'll be asked for:
- Git provider: choose between GitHub, GitLab, Bitbucket, GitHub Enterprise, GitLab Enterprise and Bitbucket Server.
- Owner username: for example
my-org. - API token
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Codecov (Sentry) tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Git provider | select | Yes |
Owner username | text | Yes |
API token | password | Yes |
Repositories (optional) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
repos | All repositories Codecov knows for the owner, with their latest coverage totals | Full refresh | — | — |
branches | A branch of a repository that has coverage data in Codecov. | Full refresh | — | — |
commits | Commits with coverage uploads on each repository's default branch, newest-first | Incremental, Full refresh | timestamp | — |
pulls | A pull request Codecov tracks for a repository, with base/head coverage totals. | Full refresh | — | — |
flags | Current coverage percentage per flag, per repository | Full refresh | — | — |
components | Current coverage percentage per component, per repository | Full refresh | — | — |
coverage_trend | Daily min/max/avg coverage time series per repository (default branch) | Incremental, Full refresh | timestamp | — |
repo_totals | Current coverage totals per repository (lines, hits, misses, partials, coverage percentage) | Full refresh | — | — |
report_files | Current coverage per file, with line-by-line coverage values | Full refresh | — | — |
report_tree | Current coverage rolled up per directory and file, following the repository's file tree | Full refresh | — | — |
test_results | Individual test runs from Test Analytics, with outcome, duration and failure message | Full refresh | — | — |
users | Members of the Codecov organization, resolving the author usernames on commits and pulls | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.