Merge branch 'master' into ALA-872-doc-intelli-j-ide-plugin-first-draft

.github/workflows/mkdocs.yml

@@ -93,7 +93,7 @@ jobs:
           echo -e "User-agent: *\nSitemap: https://${{ env.CUSTOM_DOMAIN }}/sitemap.xml" > "./site/robots.txt"
 
       - name: Deploy docs (Latest)
-        uses: peaceiris/actions-gh-pages@v3
+        uses: peaceiris/actions-gh-pages@v4
         if: github.ref == 'refs/heads/master'
         with:
           personal_token: ${{ secrets.DEPLOYMENT_PERSONAL_ACCESS_TOKEN }}

docs/faq/code-analysis/can-i-bypass-codacy-status-check.md

@@ -0,0 +1,9 @@
+# Can I bypass 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.md#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.md#status) of the pull request detail screen.
+
+![Bypass status check for pull request](images/bypass-status-check.png)

docs/faq/code-analysis/which-metrics-does-codacy-calculate.md

@@ -82,7 +82,7 @@ Codacy calculates complexity as follows:
 
 -   The complexity value for each file is the highest cyclomatic complexity of the methods in the file.
 -   A file is considered complex if its cyclomatic complexity value is higher than the threshold [**File is complex when over**](../../repositories-configure/adjusting-quality-goals.md).
--   The complexity value of a commit or pull request is the sum of the cyclomatic complexity of the files that were changed in the commit or pull request and that have complexity higher than 4.
+-   The complexity value of a commit or pull request is the sum of the cyclomatic complexity of the files that were changed in the commit or pull request and that have a high complexity increase, defined as an increase of 4 or more.
 
 Codacy displays complexity on the following places:
 

docs/faq/repositories/how-do-i-reanalyze-my-repository.md

@@ -26,7 +26,7 @@ To reanalyze a branch in your repository:
 
     ![Selecting the last commit on a branch](images/reanalyze-repository-commits-list.png)
 
-1.  Click the icon next to the **Current status** of the commit to trigger a reanalysis. Codacy will display a message when the analysis is complete.
+1.  Click the **Reanalyze** link to trigger a reanalysis. Codacy will display the status of the reanalysis request.
 
     ![Reanalyzing a commit](images/reanalyze-repository-commit.png)
 
@@ -38,7 +38,7 @@ To reanalyze a pull request in your repository:
 
     ![Selecting a pull request](images/reanalyze-repository-prs-list.png)
 
-1.  Click the icon next to the **Current status** of the pull request to trigger a reanalysis. Codacy will display a message when the analysis is complete.
+1.  Click the **Reanalyze** button to trigger a reanalysis. Codacy will display the status of the reanalysis request.
 
     ![Reanalyzing a pull request](images/reanalyze-repository-pr.png)
 

docs/faq/troubleshooting/why-arent-duplication-metrics-being-calculated.md

@@ -10,14 +10,12 @@ When this happens, Codacy doesn't display code duplication metrics for the affec
 
     ![Duplication in the Files page](images/duplication-files.png)
 
--   The **Commits** and **Pull Request** pages display an empty **New Duplication** tab.
+-   The **Commits** and **Pull Request** pages display an empty **Duplication** tab.
 
     ![New duplication for a commit](images/duplication-commits.png)
 
 -   The analysis logs for commits won't display a duplication analysis task for the tool corresponding to the affected language.
 
-    ![Analysis logs for a commit](images/duplication-logs.png)
-
 As a workaround, if you're exceeding the maximum number of source code files:
 
 1.  Use a [Codacy configuration file](../../repositories-configure/codacy-configuration-file.md) to exclude source code files of the affected language from your project to decrease the number of files to be analyzed.

docs/release-notes/cloud/cloud-2024-03.md

@@ -0,0 +1,86 @@
+---
+rss_title: Codacy release notes RSS feed
+rss_href: /feed_rss_created.xml
+description: Release notes for Codacy Cloud March 2024.
+included_jira_versions: ['2024.03']
+codacy_tools_version_old: https://github.com/codacy/codacy-tools/releases/tag/7.10.234
+codacy_tools_version_new: https://github.com/codacy/codacy-tools/releases/tag/7.10.272
+---
+
+# Cloud March 2024
+
+These release notes are for the Codacy Cloud updates during March 2024.
+
+📢 [Visit the Codacy roadmap](https://roadmap.codacy.com) and <span class="skip-vale">let us know</span> your feedback on both new and planned product updates!
+
+## Product enhancements
+
+-   Streamlined new organization setup with a guided path for adding new organizations and a setup checklist on the [Organization overview](../../organizations/organization-overview.md) page. (ALA-825)
+-   It's now possible to display penetration testing results in the Codacy app. See how to [start pen testing with Codacy](https://go.codacy.com/pen-testing-product). (TAROT-2553)
+-   It's now possible to [unfollow a repository](../../organizations/managing-repositories.md#follow-unfollow) through the Codacy app. (PLUTO-902)
+-   In Enterprise plans where Codacy automatically manages seat usage for your organization, the billing period is now based only on the code analysis activity. Codacy app users who don’t contribute to your private repositories no longer occupy a seat. (PLUTO-867)
+
+## Bug fixes
+
+-   Fixed a bug that prevented Security and risk management items from linking to their respective Jira issues. (TAROT-2648)
+-   Fixed an issue preventing pull requests from showing on Codacy due to Git operations timeout when synchronizing the current state of a repository. (IO-1019)
+-   Fixed an issue that caused sidebar labels to overlap interactive interface elements on smaller screens. (CY-7193)
+-   Fixed a bug that prevented Codacy from calculating diff coverage correctly when the diff contained only removed files. (ALA-921)
+
+## Feature removal
+
+-   We removed the option to bulk copy code patterns between repositories and to import code pattern configurations from another repository. If you want to share tool and code pattern configurations between repositories, the recommended approach is to use a [coding standard](../../organizations/using-coding-standards.md). (ALA-826)
+
+## Tool versions
+
+Codacy Cloud now includes the tool versions below. The tools that were recently updated are highlighted in bold:
+
+-   Ameba 1.5.0
+-   Bandit 1.7.5
+-   Brakeman 4.3.1
+-   bundler-audit (deprecated) 0.9.1
+-   **[Checkov 3.2.37](https://github.com/bridgecrewio/checkov/releases/tag/3.2.37) (updated from 3.0.25)**
+-   Checkstyle 10.13.0
+-   Clang-Tidy 10.0.1
+-   CodeNarc 3.3.0
+-   CoffeeLint 5.2.11
+-   **[Cppcheck 2.13.0](https://github.com/danmar/cppcheck/releases/tag/2.13.0) (updated from 2.12.0)**
+-   Credo 1.7.2
+-   CSSLint (deprecated) 1.0.5
+-   **[dartanalyzer 3.3.3](https://github.com/dart-lang/sdk/blob/main/CHANGELOG.md) (updated from 3.3.0)**
+-   detekt 1.23.5
+-   **[ESLint 8.57.0](https://github.com/eslint/eslint/releases/tag/v8.57.0) (updated from 8.56.0)**
+-   ESLint (deprecated) 7.32.0
+-   Faux-Pas 1.7.2
+-   Flawfinder 2.0.19
+-   Gosec 2.15.0
+-   Hadolint 1.18.2
+-   Jackson Linter 2.15.2
+-   JSHint (deprecated) 2.13.6
+-   markdownlint 0.33.0
+-   PHP Mess Detector 2.14.1
+-   PHP_CodeSniffer 3.7.2
+-   PMD 6.55.0
+-   Prospector 1.10.3
+-   PSScriptAnalyzer 1.21.0
+-   **[Pylint 3.1.0](https://github.com/pylint-dev/pylint/releases/tag/v3.1.0) (updated from 3.0.3)**
+-   Pylint (deprecated) 1.9.5
+-   remark-lint 9.1.2
+-   Revive 1.3.7
+-   RuboCop 1.60.2
+-   Scalastyle 1.5.1
+-   **[Semgrep 1.66.0](https://github.com/semgrep/semgrep/releases/tag/v1.66.0) (updated from 1.61.1)**
+-   ShellCheck v0.9.0
+-   SonarC# 9.19
+-   SonarVB 8.15
+-   **[Spectral 1.18.1](https://github.com/stoplightio/spectral/releases/tag/%40stoplight%2Fspectral-rulesets-1.18.1) (updated from 1.18.0)**
+-   SpotBugs 4.8.3
+-   SQLint 0.2.1
+-   Staticcheck 2023.1.6
+-   Stylelint 15.10.3
+-   SwiftLint 0.54.0
+-   Tailor 0.12.0
+-   Trivy 0.47.0
+-   TSLint (deprecated) 6.1.3
+-   TSQLLint 1.11.1
+-   **[Unity Roslyn Analyzers 1.19.0](https://github.com/microsoft/Microsoft.Unity.Analyzers/releases/tag/1.19.0) (updated from 1.17.0)**

docs/release-notes/index.md

@@ -18,6 +18,7 @@ For product updates that are in progress or planned [visit the Codacy public roa
 
 2024
 
+-   [Cloud March 2024](cloud/cloud-2024-03.md)
 -   [Cloud February 2024](cloud/cloud-2024-02.md)
 -   [Cloud January 2024](cloud/cloud-2024-01.md)
 -   [Discontinuation of SSH keys for GitHub repositories January 15, 2024](cloud/cloud-2024-01-15-gh-repository-ssh-keys-discontinuation.md)

docs/repositories-configure/ignoring-files.md

@@ -37,7 +37,6 @@ By default, Codacy ignores all the files that match the regular expressions belo
 .*bower_components/.*
 .*vendor/.*
 .*third[_-]?[Pp]arty/.*
-.*docs?/.*
 .*samples?/.*
 .*releases?/.*
 .*builds?/.*

docs/repositories-configure/integrations/bitbucket-integration.md

@@ -6,10 +6,6 @@ description: Enable the Bitbucket integration to have pull request status, comme
 
 The Bitbucket integration incorporates Codacy on your existing Git provider workflows by reporting issues and the analysis status directly on your pull requests.
 
-When this integration is enabled, you can also create pull request comments directly from Codacy when browsing the existing repository issues on the [commit issue tabs](../../repositories/commits.md#issues-tabs) or on the [pull request issue tabs](../../repositories/pull-requests.md#issues-tabs):
-
-![Bitbucket integration for issues](images/bitbucket-integration-issues.png)
-
 ## Enabling the Bitbucket integration {: id="enabling"}
 
 To enable the Bitbucket integration, open your repository **Settings**, tab **Integrations**. When you add a new repository, Codacy enables the integration using the [default settings for your organization](../../organizations/integrations/default-git-provider-integration-settings.md).

docs/repositories-configure/integrations/github-integration.md

@@ -6,10 +6,6 @@ description: Enable the GitHub integration to have status checks, annotations, i
 
 The GitHub integration incorporates Codacy on your existing Git provider workflows by reporting issues and the analysis status directly on your pull requests.
 
-When this integration is enabled, you can also create pull request comments directly from Codacy when browsing the existing repository issues on the [commit issue tabs](../../repositories/commits.md#issues-tabs) or on the [pull request issue tabs](../../repositories/pull-requests.md#issues-tabs) of a repository:
-
-![GitHub integration for issues](images/github-integration-issues.png)
-
 ## Enabling the GitHub integration {: id="enabling"}
 
 To enable the GitHub integration, open your repository **Settings**, tab **Integrations**. When you add a new repository, Codacy enables the integration using the [default settings for your organization](../../organizations/integrations/default-git-provider-integration-settings.md).

docs/repositories-coverage/commits.md

@@ -66,9 +66,13 @@ This area displays the coverage gate status and an overview of the coverage metr
 <!--coverage-overview-end-->
 
 <!--tab-diff-start-->
+{% if page.meta.product == "coverage" %}
 ## Diff tab
+{% else %}
+## Coverage tab
+{% endif %}
 
-The **Diff** tab displays a line-by-line view of the coverage variation introduced by the {{ page.meta.page_name }}. It includes the following areas:
+The {% if page.meta.product == "coverage" %}**Diff**{% else %}**Coverage**{% endif %} tab displays a line-by-line view of the coverage variation introduced by the {{ page.meta.page_name }}. It includes the following areas:
 
 -   A **list of files** modified by the {{ page.meta.page_name }}, with additional information for each file:
 
@@ -82,7 +86,11 @@ The **Diff** tab displays a line-by-line view of the coverage variation introduc
     -   **No background**: Non-coverable line
 
 <!-- vale off -->
+{% if page.meta.product == "coverage" %}
 ![Diff tab](images/{{ page.meta.file_name }}-tab-diff.png)
+{% else %}
+![Coverage tab](images/{{ page.meta.file_name }}-tab-coverage.png)
+{% endif %}
 <!-- vale on -->
 <!--tab-diff-end-->