From 42e595c79b48a07464493d93e2d64e231da27832 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia=20Carpinteiro?= Date: Wed, 17 Apr 2024 17:59:34 +0100 Subject: [PATCH] feat: Replace re-enable with refresh --- .../why-did-codacy-stop-commenting-on-pull-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/troubleshooting/why-did-codacy-stop-commenting-on-pull-requests.md b/docs/faq/troubleshooting/why-did-codacy-stop-commenting-on-pull-requests.md index 5172294d39..ba6b7ead41 100644 --- a/docs/faq/troubleshooting/why-did-codacy-stop-commenting-on-pull-requests.md +++ b/docs/faq/troubleshooting/why-did-codacy-stop-commenting-on-pull-requests.md @@ -14,7 +14,7 @@ If you stopped receiving coverage summaries on your pull requests, please [revie 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, re-enable the GitLab or Bitbucket integration on Codacy using a dedicated service account on your Git provider: +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.