faq/code-analysis

claudiacodacy · claudiacodacy · commit 4c2560af6102 · 2025-12-23T12:20:14.000Z
diff --git a/docusaurus/docs/faq/code-analysis/can-i-bypass-codacy-status-check.mdx b/docusaurus/docs/faq/code-analysis/can-i-bypass-codacy-status-check.mdx
@@ -2,15 +2,14 @@
 title: Can I bypass Codacy status check?
 ---
 
-
 :::note
 **This will only apply to gates enforcing quality checks.** If coverage is blocking a pull request analysis, we recommend contacting your git provider admin or temporarily disabling the coverage gate on the repo and reanalyzing the pull request before enabling them again.
 :::
 
-To protect your code from unwelcome changes, you can [configure your Git workflow to block merging pull requests](../../getting-started/integrating-codacy-with-your-git-workflow.md#blocking-pull-requests) if they don't pass the Codacy status check.
+To protect your code from unwelcome changes, you can [configure your Git workflow to block merging pull requests](../../getting-started/integrating-codacy-with-your-git-workflow#blocking-pull-requests) if they don't pass the Codacy status check.
 
 However, on **very specific and exceptional situations** where your pull request merging is blocked due to an unexpected issue not related to the quality of your code, Codacy allows **repository admins** to bypass the Codacy status check for that pull request.
 
-To bypass Codacy status check for a pull request, a repository admin must click **Bypass status checks** on the [pull request status area](../../repositories/pull-requests.mdx#status) of the pull request detail screen.
+To bypass Codacy status check for a pull request, a repository admin must click **Bypass status checks** on the [pull request status area](../../repositories/pull-requests#status) of the pull request detail screen.
 
-![Bypass status check for pull request](images/bypass-status-check.png)
+![Bypass status check for pull request](./images/bypass-status-check.png)
diff --git a/docusaurus/docs/faq/code-analysis/does-codacy-check-for-dependencies.mdx b/docusaurus/docs/faq/code-analysis/does-codacy-check-for-dependencies.mdx
@@ -2,7 +2,6 @@
 title: Does Codacy check for dependencies?
 ---
 
-
 Yes, Codacy scans the manifest files of your repositories and displays any vulnerable dependencies as Codacy issues.
 
-For a list of supported languages and manifest files scanned by the Codacy dependency vulnerability scanning tools, see [Supported languages and tools](../../getting-started/supported-languages-and-tools.md).
+For a list of supported languages and manifest files scanned by the Codacy dependency vulnerability scanning tools, see [Supported languages and tools](../../getting-started/supported-languages-and-tools).
diff --git a/docusaurus/docs/faq/code-analysis/does-codacy-place-limits-on-the-code-analysis.mdx b/docusaurus/docs/faq/code-analysis/does-codacy-place-limits-on-the-code-analysis.mdx
@@ -2,16 +2,15 @@
 title: Does Codacy place limits on the code analysis?
 ---
 
-
 Codacy uses limits when performing the analysis of your repositories to ensure good performance levels and avoid degradation of service during peak load.
 
 The following table describes these limits and includes links to more information and workarounds, if available:
 
-<!--NOTE
+{/*<!--NOTE
     See the comments in this Jira task for more background information on the limits listed on this page:
 
     https://codacy.atlassian.net/browse/CY-3232
--->
+-->*/}
 
 <table>
 <thead>
@@ -36,7 +35,7 @@ See <a href="../../troubleshooting/why-is-my-file-over-150-kb-missing/">Why is m
 <td>10 MB</td>
 <td>
 Codacy doesn't parse code coverage reports that are over the file size limit.<br/><br/>
-See <a href="../../../coverage-reporter/troubleshooting-coverage-cli-issues/#jsonparseexception-while-uploading-coverage-data">JsonParseException while uploading coverage data</a>
+See <a href="../../../coverage-reporter/troubleshooting-coverage-cli-issues#jsonparseexception-while-uploading-coverage-data">JsonParseException while uploading coverage data</a>
 </td>
 </tr>
 
@@ -79,4 +78,4 @@ If you believe that you may have hit any of these limits and need help to overco
 
 ## See also
 
--   [Which metrics does Codacy calculate?](which-metrics-does-codacy-calculate.md)
+-   [Which metrics does Codacy calculate?](./which-metrics-does-codacy-calculate)
diff --git a/docusaurus/docs/faq/code-analysis/how-long-does-it-take-for-my-repository-to-be-analyzed.md b/docusaurus/docs/faq/code-analysis/how-long-does-it-take-for-my-repository-to-be-analyzed.md
diff --git a/docusaurus/docs/faq/code-analysis/how-long-does-it-take-for-my-repository-to-be-analyzed.mdx b/docusaurus/docs/faq/code-analysis/how-long-does-it-take-for-my-repository-to-be-analyzed.mdx
@@ -0,0 +1,23 @@
+---
+title: How long does it take for my repository to be analyzed?
+---
+
+Codacy usually takes under 5 minutes to analyze your repository. It may however take longer, depending on a number of factors:
+
+- **Whether it's the initial analysis of your repository**  
+  The initial analysis examines all files in the repository, while each subsequent commit triggers an analysis only on files changed in that commit.
+
+- **Whether tool configurations have been updated**  
+  Updates to tool configurations trigger a reanalysis of all files in the repository on the next commit and may impact analysis duration.
+
+- **The size of your repository**  
+  To speed up the analysis, [ignore any files and directories](../../repositories-configure/ignoring-files) that aren't relevant to your project, such as generated code or any third-party libraries included in your repositories.
+
+- **The time it takes your Git provider to trigger the analysis**  
+  Codacy relies on post-commit hooks sent by your Git provider to trigger the analysis after each push to the repository, so if your analysis is taking a lot of time to start [check that the Post-Commit Hook integration for your repository is enabled](../../repositories-configure/integrations/post-commit-hooks).
+
+- **The priority of your analysis request and the current load on Codacy's servers**  
+  Open-source projects have lower priority in the Codacy analysis queues.
+
+- **Whether Codacy or your Git provider is currently experiencing issues or outages**  
+  Check the [Codacy status page](https://status.codacy.com/) and the status page of your Git provider ([GitHub](https://www.githubstatus.com/), [GitLab](https://status.gitlab.com/), [Bitbucket](https://bitbucket.status.atlassian.com/)) to see if there is any ongoing incident that could delay the analysis.
diff --git a/docusaurus/docs/faq/code-analysis/how-to-configure-php-codesniffer-coding-standards.mdx b/docusaurus/docs/faq/code-analysis/how-to-configure-php-codesniffer-coding-standards.mdx
@@ -3,18 +3,15 @@ title: How to configure PHP_CodeSniffer coding standards?
 description: To enforce a specific PHP_CodeSniffer coding standard on Codacy you must create a configuration file on the root of your repository that references one or more coding standards.
 ---
 
-
-By default, Codacy uses the PHP_CodeSniffer configuration on the [Code patterns](../../repositories-configure/configuring-code-patterns.md) page when analyzing your repositories.
+By default, Codacy uses the PHP_CodeSniffer configuration on the [Code patterns](../../repositories-configure/configuring-code-patterns) page when analyzing your repositories.
 
 To enforce a specific PHP_CodeSniffer coding standard you must [create a configuration file](https://github.com/squizlabs/PHP_CodeSniffer/wiki/Advanced-Usage#using-a-default-configuration-file) on the root of your repository that references one or more of the following coding standards:
 
--   Default coding standards packaged together with PHP_CodeSniffer:
-
-	    [PHP_CodeSniffer coding standards](https://github.com/squizlabs/PHP_CodeSniffer/tree/master/src/Standards)
-
--   Additional coding standards that Codacy packages on the PHP_CodeSniffer tool plugin. Check the repository the additional coding standards to learn how you can reference them in your configuration files:
+- Default coding standards packaged together with PHP_CodeSniffer:  
+  [PHP_CodeSniffer coding standards](https://github.com/squizlabs/PHP_CodeSniffer/tree/master/src/Standards)
 
-	    [codacy-codesniffer composer.json](https://github.com/codacy/codacy-codesniffer/blob/master/composer.json)
+- Additional coding standards that Codacy packages on the PHP_CodeSniffer tool plugin. Check the repository the additional coding standards to learn how you can reference them in your configuration files:  
+  [codacy-codesniffer composer.json](https://github.com/codacy/codacy-codesniffer/blob/master/composer.json)
 
 For example, create a text file with the name `phpcs.xml` to use the PSR12 coding standard but excluding the sniffs `Generic.WhiteSpace.DisallowTabIndent` and `PSR12.Operators.OperatorSpacing`:
 
diff --git a/docusaurus/docs/faq/code-analysis/how-to-skip-an-analysis.mdx b/docusaurus/docs/faq/code-analysis/how-to-skip-an-analysis.mdx
@@ -2,7 +2,6 @@
 title: How to skip an analysis?
 ---
 
-
 By default, Codacy automatically analyzes a repository whenever you push changes. However, you can override this behavior by adding one of the "skip" tags - `[ci skip]`, `[skip ci]`, `[codacy skip]` or `[skip codacy]` - anywhere in the subject or body of the commit message. For example:
 
 ```bash
diff --git a/docusaurus/docs/faq/code-analysis/which-metrics-does-codacy-calculate.mdx b/docusaurus/docs/faq/code-analysis/which-metrics-does-codacy-calculate.mdx
diff --git a/docusaurus/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.mdx b/docusaurus/docs/faq/code-analysis/why-does-codacy-show-unexpected-coverage-changes.mdx
