Skip to content

Why did Codacy stop commenting on pull requests?#

Outdated app permissions#

This section applies to Codacy Coverage on GitHub

Coverage information is currently sent to GitHub by a new version of the Codacy Coverage engine, which depends on updated app permissions.

If you stopped seeing coverage information in the pull request summaries, please review and accept the updated Codacy app permissions on GitHub. For more information on the rollout of the new Coverage engine, see the relevant release note.

Outdated permissions or invalid SSH key#

This section applies to GitLab and Bitbucket

Different reasons can cause Codacy to stop analyzing and commenting on pull requests, but the most common is that the user who initially enabled the GitLab or Bitbucket integration no longer has permissions on the repository or that the SSH key is no longer valid.

To fix this issue and avoid future disruptions, refresh the GitLab or Bitbucket integration on Codacy using a dedicated service account on your Git provider:

  1. Create a service account on your Git provider exclusively dedicated to integrating Codacy with your repositories.

    Note

    The service account must:

    • Have administrator permissions on the repositories to integrate with Codacy
    • Not be shared by other systems to ensure that Codacy doesn't hit the API rate limits of the Git provider when using this account

    Tip

    Using a dedicated service account also has the advantage of any pull request comments made by Codacy appearing as authored by the service account instead of by a regular organization member. You can name this account "Codacy" and use this Codacy logo as the account picture so that your pull request comments look like the following example:

    Codacy comment on a GitLab merge request

  2. Log out of both your Git provider and of Codacy.

  3. Log in to Codacy using the new service account.

  4. Open your repository Settings, tab Integrations, and click the link Refresh connection to refresh the existing Git provider integration:

    Refresh Git provider integration

  5. Make sure the Git provider integration is configured as needed:

See also#

Was this page helpful?

Your feedback helps us improve the documentation.

Edit this page on GitHub Contact support