Codecov: FAQ and troubleshooting

Why doesn't the gutter show my branch's coverage?

The editor gutter shows the coverage of the repository's default branch, as described in Which coverage the editor shows. To see the coverage effect of your current branch, use the Codecov Metrics dashboard or folder coverage.

Why does a file show no coverage?

If a file shows no coverage at all, check the following:

• Your CI uploaded a coverage report to Codecov for the default branch, and the report includes the file.

• The file paths in the report match the paths in the Git repository.

• Coverage is not hidden. If the editor context menu shows Show Codecov Coverage, select it.

• The project is connected and the repository is detected in Settings | Tools | Codecov.

• Coverage has loaded for the file. To load it, right-click in the editor and select Refresh Codecov Coverage.

Why are the coverage bars on the wrong lines?

The gutter places the bars by the line numbers of the file version that Codecov measured, from the latest report on the default branch. If your local file has added or removed lines compared with that version, the bars below those lines sit next to the wrong lines. To see the measured version, click a coverage bar and click Open in Codecov. For details, see Which coverage the editor shows.

Why is no repository detected?

The settings page shows "No repository detected. Please verify your project settings.", or Test Connection reports that it could not detect the repository.

• Make sure the project is a Git repository with a remote that points to GitHub, GitLab or Bitbucket.

• Make sure Service Provider matches the host of that remote.

• Make sure the repository is activated on Codecov and your token's account can access it.

The end of the Test Connection warning gives the reason:

No local repository detected for this project

None of the project's Git remotes is on the host that matches Service Provider: github.com for Github, gitlab.com for Gitlab or bitbucket.org for Bitbucket. If you changed Service Provider after you opened the project, click OK, reopen the project and test again.

No matching repository found for 'demo-project'.

Codecov lists no activated repository with that name for the owner in the remote URL.

Repository detection failed: …

The plugin could not get the owner's repositories from Codecov. The text after the colon is the error. If you changed Server URL after you opened the project, click OK, reopen the project and test again.

How do I fix a failed connection test?

Connection Test Failed with "Connection failed. Please check your token." usually means the API token is wrong, revoked or expired, or Server URL is wrong.

For a self-hosted Codecov server, check that Server URL is the base URL of that server.

Does the plugin support private repositories?

Yes. The plugin shows coverage for any repository that the account of your API token can access on Codecov.

Why is the Codecov Metrics button disabled?

The Codecov Metrics button is enabled after the plugin detects the project's Codecov repository. Connect the project as described in Codecov: Install and connect, then reopen the project if needed.

Why does the dashboard report no repository?

The dashboard shows "Error: No Codecov repository detected." when it loads data while the project has no detected Codecov repository, for example after you disconnect the project. Check the connection in Settings | Tools | Codecov, then click Refresh on the Codecov Metrics toolbar.

Why does the dashboard show no pull request impact?

The dashboard shows "No Codecov compare report available for the current branch." in these cases:

• You are on the default branch, which has nothing to compare.

• Codecov has no processed commit of the current branch yet. Push the branch and wait for CI to upload coverage, then click Refresh on the Codecov Metrics toolbar.

Why are there no coverage dots on folders?

• Folder coverage is off by default. Turn on Show Coverage on Folders on the Codecov Metrics toolbar.

• Codecov has no report for the current branch. The warning "Codecov: no coverage data for this branch" appears when you turn the feature on.

• The folder has no files in the Codecov report.

• Show Coverage on Folders is disabled, and its tooltip shows "Connect to Codecov to enable folder coverage" or "No Codecov repository mapped for this project". Check the connection in Settings | Tools | Codecov, then click Refresh on the Codecov Metrics toolbar.

Why can't I validate codecov.yml?

• "Codecov API token is missing. Please configure it in Settings." means that validation needs the API token. Set it as described in Codecov: Install and connect.

• While Inject codecov YAML schema is on, Validate Codecov YAML is offered only for files named exactly codecov.yml or codecov.yaml. Keep that option on, because otherwise the menu item appears for every file. Completion also works in files such as .codecov.yml, but validation does not.

How do I report a bug?

When the IDE shows an error from the plugin, open the error details and click Report Exception. A prefilled issue opens in the edgafner/dorkag repository on GitHub, with the plugin, IDE and operating system versions. Add the steps that lead to the error and submit the issue.

You can also open an issue directly in that repository. For other ways to get help, see Codecov: Support.