Merge branch 'master' of https://github.com/codacy/docs

Author: stefanvacareanu7

.gitignore

@@ -22,3 +22,10 @@ tools/*.csv
 
 #Ignore vscode AI rules
 .github/copilot-instructions.md
+
+#Ignore cursor AI rules
+.cursor/rules/codacy.mdc
+
+#Ignore vscode AI rules
+.github/instructions/codacy.instructions.md
+

docs/codacy-api/images/codacy-api-tokens-account-modal.png

@@ -43,6 +43,7 @@ Besides real-time AI code scanning, Guardrails users can now prompt all their Co
 - PMD
 - dartanalyzer
 - [Lizard](https://docs.codacy.com/release-notes/cloud/cloud-2025-02-adding-ruff-lizard/#lizard)
+- Revive
 
 ## How to install - Quick Guide {: id="how-to-install-quick-guide"}
 

docs/codacy-api/images/codacy-api-tokens-account-table.png

@@ -23,4 +23,12 @@ npm install -g @codacy/codacy-mcp
     }
   }
 }
-```
+```
+
+## GitHub Copilot
+
+### MCP Policy Requirement
+
+If Copilot doesn't find any MCP servers or tools, you might be missing the required policy setting. If you are a member of an organization or enterprise with a Copilot Business or Copilot Enterprise plan, the "MCP servers in Copilot" policy must be enabled in order to use MCP with Copilot. This policy can be configured by organization owners in the Copilot settings.
+
+For more information about enabling this policy, see the [GitHub documentation on MCP prerequisites](https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp#prerequisites).

docs/codacy-api/images/codacy-api-tokens-account.png

@@ -8,11 +8,13 @@ Codacy performs static code analysis and calculates code duplication, code compl
 
 The following sections describe how Codacy calculates each supported metric and where you can see each metric on the Codacy UI:
 
--   [Grade](#grade)
--   [Issues](#issues)
--   [Complexity](#complexity)
--   [Duplication](#duplication)
--   [Code coverage](#code-coverage)
+- [Which metrics does Codacy calculate?](#which-metrics-does-codacy-calculate)
+  - [Grade](#grade)
+  - [Issues](#issues)
+  - [Complexity](#complexity)
+  - [Duplication](#duplication)
+  - [Code coverage](#code-coverage)
+  - [See also](#see-also)
 
 !!! note
     Depending on certain characteristics of your repository, such as the number of source code files and their size, Codacy may [apply limits to the code analysis](does-codacy-place-limits-on-the-code-analysis.md) that impact the calculation of the supported metrics.
@@ -51,7 +53,7 @@ Codacy calculates the number of issues in the following static code analysis cat
 <!--issue-categories-start-->
 -   **Code style:** Code formatting and syntax problems, such as variable names style and enforcing the use of brackets and quotation marks
 -   **Error prone:** Code that may hide bugs and language keywords that should be used with caution, such as the operator `==` in JavaScript or `Option.get` in Scala
--   **Code complexity:** High complexity methods and classes that should be refactored
+-   **Code complexity:** High complexity files that should be refactored
 -   **Performance:** Code that can have performance problems
 -   **Compatibility:** Mainly for frontend code, compatibility problems across different browser versions
 -   **Unused code:** Unused variables and methods, code that can't be reached
@@ -88,8 +90,8 @@ Codacy displays complexity on the following places:
 
 |Place|Metric|
 |-----|------|
-|[Commit detail page](../../repositories/commits.md)<br/>[Pull request detail page](../../repositories/pull-requests.md)<br/>[Email notifications](../../account/emails.md#managing-your-email-notifications)|Variation of the complexity value introduced by the commit or pull request|
-|[Files page](../../repositories/files.md)|Complexity value of each file|
+|[Commit detail page](../../repositories/commits.md)<br/>[Pull request detail page](../../repositories/pull-requests.md)<br/>[Email notifications](../../account/emails.md#managing-your-email-notifications)|The complexity variation introduced by a commit or pull request is defined as the sum of the changes in code complexity for each file modified in the commit or pull request|
+|[Files page](../../repositories/files.md)|The file complexity value is the sum of the complexity values of all methods defined within the file|
 |[Repository Dashboard](../../repositories/repository-dashboard.md)|Percentage of complex files in your repository and how the metric is evolving over time|
 |[Organization overview](../../organizations/organization-overview.md)|Average percentage of complex files in the repositories in your organization and percentage of complex files in each repository|
 |[Repositories list page](../../organizations/managing-repositories.md)|Percentage of complex files in each repository in your organization|

docs/codacy-guardrails/codacy-guardrails-getting-started.md

@@ -1,6 +1,6 @@
 # Integrating Codacy with IntelliJ IDEs
 
-The [Codacy IntelliJ plugin](https://github.com/codacy/codacy-intellij-extension) is an open-source plugin for IntelliJ IDEs that lets you review the result of the Codacy analysis for a pull request, get the full list of problems found, and navigate to any Quality issue that you want to review and fix.
+The [Codacy IntelliJ plugin](https://github.com/codacy/codacy-intellij-extension) is an open-source plugin for IntelliJ IDEs that lets you review the result of the Codacy analysis for a pull request, get the full list of problems found, and navigate to any issue that you want to review and fix.
 
 !!! info "To use this plugin you need a [Codacy account](https://www.codacy.com/signup-codacy)"
 
@@ -12,15 +12,15 @@ The main view of the Codacy IntelliJ plugin provides a summary of the code quali
 
 In the main view, you can find the following information:
 
--   The **Quality status** of the pull request, either up to standards or not up to standards, based on the [Quality gates](../repositories-configure/adjusting-quality-gates.md) set for the repository.
+-   The **Status** of the pull request, either up to standards or not up to standards, based on the [Gates](../repositories-configure/adjusting-quality-gates.md) set for the repository.
 
--   Any **Quality issues** introduced or fixed by the pull request. These are the same issues you find in the [Quality Issues tabs](../repositories/pull-requests.md#issues-tabs) in the Codacy app and are also visible in IntelliJ's Problems tab.
+-   Any **issues** introduced or fixed by the pull request. These are the same issues you find in the [Issues tabs](../repositories/pull-requests.md#issues-tabs) in the Codacy app and are also visible in IntelliJ's Problems tab.
 
-    When this item is expanded, the number next to each file name is the total number of Quality issues that the pull request adds to that file.
+    When this item is expanded, the number next to each file name is the total number of issues that the pull request adds to that file.
 
 -   The **diff coverage** introduced by the pull request. The percentage next to each file name is the coverage variation for that file.
 
--   Sequences of **duplicate code** (clones) introduced by the pull request. These are the same ones you find in the [Quality Duplication tabs](../repositories/pull-requests.md#duplication-tabs) in the Codacy app.
+-   Sequences of **duplicate code** (clones) introduced by the pull request. These are the same ones you find in the [Duplication tabs](../repositories/pull-requests.md#duplication-tabs) in the Codacy app.
 
 -   Variations in **code complexity** introduced by the pull request.
 
@@ -56,12 +56,12 @@ After completing these steps, the main view shows the result of the latest Codac
 
 ## Reviewing pull request issues
 
-In the **Problems tool window**, Codacy displays the same Quality issues you find in the main view and lets you navigate to the exact line of code where the issue was found.
+In the **Problems tool window**, Codacy displays the same issues you find in the main view and lets you navigate to the exact line of code where the issue was found.
 
 !!! note
     Code coverage, duplicates, and complexity aren't currently shown in the Problems tool window.
 
-To review Quality issues:
+To review issues:
 
 1.  Open the file you want to review.
 

docs/codacy-guardrails/codacy-guardrails-troubleshooting.md

@@ -2,7 +2,7 @@
 
 The [Codacy Visual Studio Code extension](https://github.com/codacy/codacy-vscode-extension) is an open-source project that enables developers to review directly in VS Code the result of Codacy analysis for the pull requests they’re working on.
 
-Use this extension to get the full list of problems found by Codacy for a pull request and navigate to any Quality issue that you want to review and fix.
+Use this extension to get the full list of problems found by Codacy for a pull request and navigate to any issue that you want to review and fix.
 
 !!! info "To use this extension you need a [Codacy account](https://www.codacy.com/signup-codacy)"
 
@@ -20,11 +20,11 @@ The main view of the extension displays information about the code quality and c
 
 The **Pull request status** tab displays the following information for the pull request of the currently checked-out branch:
 
--   The **Quality status** of the pull request, either up to standards or not up to standards, based on the [Quality gates](../repositories-configure/adjusting-quality-gates.md) set for the repository.
+-   The **Status** of the pull request, either up to standards or not up to standards, based on the [Gates](../repositories-configure/adjusting-quality-gates.md) set for the repository.
 
--   Any **Quality issues** introduced or fixed by the pull request. These are the same issues you find in the [Quality Issues tabs](../repositories/pull-requests.md#issues-tabs) in the Codacy app and are also visible in VS Code's Problems tab.
+-   Any **issues** introduced or fixed by the pull request. These are the same issues you find in the [Issues tabs](../repositories/pull-requests.md#issues-tabs) in the Codacy app and are also visible in VS Code's Problems tab.
 
-    When this item is expanded, the number next to each file name is the total number of Quality issues that the pull request adds to or removes from that file. The number farther to the right, added by VS Code, is the total number of problems in that file, which may or may not be Quality issues from Codacy. If there are any Medium or Critical Quality issues, the file name is also highlighted in yellow (Medium) or red (Critical).
+    When this item is expanded, the number next to each file name is the total number of issues that the pull request adds to or removes from that file. The number farther to the right, added by VS Code, is the total number of problems in that file, which may or may not be issues from Codacy. If there are any Medium or Critical issues, the file name is also highlighted in yellow (Medium) or red (Critical).
 
     ![Important issues](./images/codacy-vscode-extension-important-issues.png)
 
@@ -34,7 +34,7 @@ The **Pull request status** tab displays the following information for the pull
 
     ![Toggle inline coverage](./images/codacy-vscode-extension-inline-coverage.png)
 
--   Sequences of **duplicate code** (clones) introduced by the pull request. These are the same ones you find in the [Quality Duplication tabs](../repositories/pull-requests.md#duplication-tabs) in the Codacy app.
+-   Sequences of **duplicate code** (clones) introduced by the pull request. These are the same ones you find in the [Duplication tabs](../repositories/pull-requests.md#duplication-tabs) in the Codacy app.
 
 -   Variations in **code complexity** introduced by the pull request.
 
@@ -48,23 +48,23 @@ The **Open Pull Requests** tab lists all open pull requests for the repository,
 
     -   Analyzing, if Codacy is analyzing the branch.
 
-    -   Up to standards or not up to standards, based on the [Quality gates](../repositories-configure/adjusting-quality-gates.md) set for the repository.
+    -   Up to standards or not up to standards, based on the [Gates](../repositories-configure/adjusting-quality-gates.md) set for the repository.
 
 -   The author of the pull request.
 
 -   The source and target branches of the pull request.
 
--   Any **Quality issues** introduced or fixed by the pull request. These are the same issues you find in the [Quality Issues tabs](../repositories/pull-requests.md#issues-tabs) in the Codacy app.
+-   Any **issues** introduced or fixed by the pull request. These are the same issues you find in the [Issues tabs](../repositories/pull-requests.md#issues-tabs) in the Codacy app.
 
--   Sequences of **duplicate code** (clones) introduced by the pull request. These are the same ones you find in the [Quality Duplication tabs](../repositories/pull-requests.md#duplication-tabs) in the Codacy app.
+-   Sequences of **duplicate code** (clones) introduced by the pull request. These are the same ones you find in the [Duplication tabs](../repositories/pull-requests.md#duplication-tabs) in the Codacy app.
 
 -   Variations in **code complexity** introduced by the pull request. This is the same value you find on the [Pull request quality overview](../repositories/pull-requests.md#quality-overview) in the Codacy app.
 
 ### Analyzed branch tab
 
 ![Analyzed branch tab UI](images/codacy-vscode-extension-analyzed-branch-tab.png)
 
-The **Analyzed Branch** tab appears if you switch to an analyzed branch that doesn't have an open pull request, such as the `main` or `master` branch. This tab shows an overview of the Quality issues found in that branch, grouped by recently added, introduced by the current user, issue category, and issue severity.
+The **Analyzed Branch** tab appears if you switch to an analyzed branch that doesn't have an open pull request, such as the `main` or `master` branch. This tab shows an overview of the issues found in that branch, grouped by recently added, introduced by the current user, issue category, and issue severity.
 
 See [how to manage the analysis of your repository's branches](../repositories-configure/managing-branches.md).
 
@@ -99,16 +99,16 @@ To see Codacy quality and coverage data for an open pull request, follow these s
 
 1.  Check out the pull request of interest. You can do it either manually or from the **Open Pull Requests** tab, by clicking the arrow button or using the contextual right-click menu.
 
-After completing these steps, the main view shows the result of the latest Codacy analysis for the pull request. The VS Code Problems tab lists the Quality issues found.
+After completing these steps, the main view shows the result of the latest Codacy analysis for the pull request. The VS Code Problems tab lists the issues found.
 
 ## Reviewing pull request issues
 
-In the **Problems tab**, Codacy displays the same Quality issues you find in the **Status tab** and lets you navigate to the exact line of code where the issue was found.
+In the **Problems tab**, Codacy displays the same issues you find in the **Status tab** and lets you navigate to the exact line of code where the issue was found.
 
 !!! note
     Code coverage, duplicates, and complexity aren't currently shown in the Problems tab.
 
-To review Quality issues:
+To review issues:
 
 1.  Open the **Problems tab** (use `Ctrl+Shift+M` on Windows/Linux or `Cmd+Shift+M` on macOS).