migrate all includes

Author: claudiacodacy

…ries/how-do-i-reanalyze-my-repository.md …ies/how-do-i-reanalyze-my-repository.mdxnew-docs/src/content/docs/faq/repositories/how-do-i-reanalyze-my-repository.md renamed to new-docs/src/content/docs/faq/repositories/how-do-i-reanalyze-my-repository.mdx new-docs/src/content/docs/faq/repositories/how-do-i-reanalyze-my-repository.md renamed to new-docs/src/content/docs/faq/repositories/how-do-i-reanalyze-my-repository.mdx

@@ -1,9 +1,10 @@
 ---
 title: How do I reanalyze my repository?
 ---
+import AdminAccessControlInfo from './../../../includes/AdminAccessControlInfo.astro'
 
 
-{% include-markdown "../../assets/includes/admin-access-control-info.md" %}
+<AdminAccessControlInfo />
 
 Reanalyze the last commit in your branch or pull request:
 

…g-started/configuring-your-repository.md …-started/configuring-your-repository.mdxnew-docs/src/content/docs/getting-started/configuring-your-repository.md renamed to new-docs/src/content/docs/getting-started/configuring-your-repository.mdx new-docs/src/content/docs/getting-started/configuring-your-repository.md renamed to new-docs/src/content/docs/getting-started/configuring-your-repository.mdx

@@ -3,9 +3,9 @@ title: Configuring your repository
 description: Configure Codacy to match the coding conventions and best practices that your team may already be following or that you want to promote.
 nav_step: 1
 ---
+import NavMultistep from './../../includes/NavMultistep.astro'
 
-
-{% include-markdown "../assets/includes/nav-multistep-quickstart.md" %}
+<NavMultistep step={1} />
 
 Once you've added your first repository, it's important that you configure Codacy's analysis tools to match the use cases of your team, such as configuring any coding conventions and best practices that your team may already be following or that you want to promote. It's also critical to review the configurations to avoid reporting false positives or any other issues that don't bring value to your team, which can introduce unwanted delays to the development process.
 
@@ -17,13 +17,13 @@ To configure your repository, follow these steps:
 1.  [Configuring code patterns](#configuring-code-patterns)
 1.  [Adding coverage reports](#adding-coverage) (optional)
 
-## 1. Ignoring files {#ignoring-files}
+## 1. Ignoring files \{#ignoring-files\}
 
 [Ignore any files and directories](../repositories-configure/ignoring-files.md) that aren't relevant for the Codacy analysis, such as generated code or any third-party libraries included in your repositories.
 
 ![Ignoring files](../repositories-configure/images/ignored-files.png)
 
-## 2. Configuring code patterns {#configuring-code-patterns}
+## 2. Configuring code patterns \{#configuring-code-patterns\}
 [Configure the tools and code patterns](../repositories-configure/configuring-code-patterns.md) that Codacy uses to analyze your repository. If security is important for your team, review the [Security and risk management dashboard](../organizations/managing-security-and-risk.md) to ensure that your configuration detects potential security issues.
 
 :::tip
@@ -32,14 +32,14 @@ To ensure that multiple repositories consistently follow the same global tool an
 
 ![Configuring the tools and code patterns](../repositories-configure/images/code-patterns.png)
 
-## 3. Adding coverage to your repository (optional) {#adding-coverage}
+## 3. Adding coverage to your repository (optional) \{#adding-coverage\}
 If you want to use code coverage to block merging pull requests that don't meet your quality standards, make sure that you [add coverage to your repository](../coverage-reporter/index.md).
 
 It's important that you set up coverage beforehand because Codacy can only report the coverage status for pull requests after receiving reports for the last commits **on both the pull request branch and the target branch**.
 
 ![Adding coverage to your repository](../coverage-reporter/images/coverage-codacy-ui.png)
 
-## Next steps {#next-steps}
+## Next steps \{#next-steps\}
 Once you’re satisfied with your setup, [integrate Codacy with your Git workflow](integrating-codacy-with-your-git-workflow.md) to flag potential issues, block problematic pull requests, and display other useful suggestions directly on your Git provider.
 
 :::tip

…grating-codacy-with-your-git-workflow.md …rating-codacy-with-your-git-workflow.mdxnew-docs/src/content/docs/getting-started/integrating-codacy-with-your-git-workflow.md renamed to new-docs/src/content/docs/getting-started/integrating-codacy-with-your-git-workflow.mdx new-docs/src/content/docs/getting-started/integrating-codacy-with-your-git-workflow.md renamed to new-docs/src/content/docs/getting-started/integrating-codacy-with-your-git-workflow.mdx

@@ -3,9 +3,10 @@ title: Integrating Codacy with your Git workflow
 description: Integrate Codacy with your Git workflow to display analysis results and code coverage as status checks on your pull requests and optionally block merging pull requests.
 nav_step: 2
 ---
+import NavMultistep from './../../includes/NavMultistep.astro'
+import DefaultGitProviderSettingsTip from './../../includes/DefaultGitProviderSettingsTip.astro'
 
-
-{% include-markdown "../assets/includes/nav-multistep-quickstart.md" %}
+<NavMultistep step={2} />
 
 Once you've configured your repository to best match your use case, integrate Codacy with your Git workflow to display analysis results and code coverage as status checks on your pull requests.
 
@@ -17,7 +18,7 @@ To integrate Codacy with your Git workflow, follow these steps:
 1.  [Configuring the Git provider integration](#git-provider-integration)
 1.  [Blocking merging pull requests](#blocking-pull-requests) (optional)
 
-## 1. Configuring the quality gate rules {#configuring-gate}
+## 1. Configuring the quality gate rules \{#configuring-gate\}
 [Review and adjust the quality gates](../repositories-configure/adjusting-quality-gates.md) of your repository to decide which pull requests should fail the Codacy quality gate.
 
 :::tip
@@ -28,7 +29,6 @@ Codacy generally recommends that on a first stage you configure rules that focus
 -   High severity issues
 -   Security issues
 -   Considerable drops in code coverage
-
 :::
 
 :::caution
@@ -37,18 +37,14 @@ Codacy generally recommends that on a first stage you configure rules that focus
 
 ![Adjusting the quality gates](../repositories-configure/images/quality-settings-gates.png)
 
-## 2. Configuring the Git provider integration {#git-provider-integration}
+## 2. Configuring the Git provider integration \{#git-provider-integration\}
 Make sure you enable the option **Status checks** ([GitHub](../repositories-configure/integrations/github-integration.md#status-checks)) or **Pull request status** ([GitLab](../repositories-configure/integrations/gitlab-integration.md#pull-request-status) and [Bitbucket](../repositories-configure/integrations/bitbucket-integration.md#pull-request-status)).
 
-{%
-    include-markdown "../assets/includes/default-git-provider-settings-tip.md"
-    start="<!--default-settings-start-->"
-    end="<!--default-settings-end-->"
-%}
+<DefaultGitProviderSettingsTip />
 
 ![Enabling your Git provider integration](../repositories-configure/integrations/images/github-integration.png)
 
-## 3. Blocking merging pull requests (optional) {#blocking-pull-requests}
+## 3. Blocking merging pull requests (optional) \{#blocking-pull-requests\}
 Once you've tested out Codacy for a while and you're happy with the level of feedback provided, you can decide to enforce the quality gates and use Codacy to block merging pull requests on your Git provider. This is the best way to protect your code from unwelcome changes and fully integrate code quality and coverage analysis into your development pipeline.
 
 :::caution

…s/organizations/organization-overview.md …/organizations/organization-overview.mdxnew-docs/src/content/docs/organizations/organization-overview.md renamed to new-docs/src/content/docs/organizations/organization-overview.mdx new-docs/src/content/docs/organizations/organization-overview.md renamed to new-docs/src/content/docs/organizations/organization-overview.mdx

@@ -2,6 +2,7 @@
 title: Organization overview
 description: The Organization overview provides an overview of the repositories belonging to your Git provider organization. Here you can compare their statuses and check for items that require your attention.
 ---
+import DashboardApiReportNote from './../../includes/DashboardApiReportNote.astro'
 
 
 The **Organization overview** provides an overview of the repositories belonging to your Git provider organization that you [follow on Codacy](managing-repositories.md). Here you can compare their statuses and check for items that require your attention.
@@ -20,7 +21,7 @@ On this page, you can also see the **Organization setup** area, which provides y
 
 The following sections provide a detailed description of the repository-related dashboard areas.
 
-{% include-markdown "../assets/includes/dashboard-api-report-note.md" %}
+<DashboardApiReportNote />
 
 ## Overall quality chart
 
@@ -30,7 +31,6 @@ The **Overall quality** chart compares the repositories that you follow regardin
 -   The overall quality chart calculates metrics and displays data only for the **repositories that you follow** on Codacy. This means that depending on their list of followed repositories, two users can see different results on this chart.
 
 -   The overall quality chart displays information for **at most the last 100 updated repositories**.
-
 :::
 
 ![Overall quality chart](images/organization-overview-overall-quality.png)
@@ -56,7 +56,7 @@ The **Last updated repositories** list displays the last updated repositories, s
 :::note
 The exact value of the last updated date of the repositories depends on your Git provider:
 
--   **GitHub:** date of the last commit to any branch of the repository (value of `pushed_at` from the [GitHub Repositories API](https://docs.github.com/en/rest/repos/repos#list-organization-repositories){: target=_"blank"}).
+-   **GitHub:** date of the last commit to any branch of the repository (value of `pushed_at` from the [GitHub Repositories API](https://docs.github.com/en/rest/repos/repos#list-organization-repositories)).
 -   **GitLab:** date when the project was last updated (value of `last_activity_at` from the [GitLab Groups API](https://docs.gitlab.com/ee/api/groups.html)). Note that this value is only updated [at most once per hour](https://gitlab.com/gitlab-org/gitlab/-/issues/20952)).
 -   **Bitbucket:** date when the repository was last updated (value of `updated_on` from the [Bitbucket Repositories API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/#api-group-repositories)). **On Bitbucket Server** Codacy can't obtain this information and the list displays the repositories in alphabetical order.
 

…les-and-permissions-for-organizations.md …es-and-permissions-for-organizations.mdxnew-docs/src/content/docs/organizations/roles-and-permissions-for-organizations.md renamed to new-docs/src/content/docs/organizations/roles-and-permissions-for-organizations.mdx new-docs/src/content/docs/organizations/roles-and-permissions-for-organizations.md renamed to new-docs/src/content/docs/organizations/roles-and-permissions-for-organizations.mdx

@@ -2,6 +2,7 @@
 title: Roles and permissions for organizations
 description: List of operations that users can perform on Codacy depending on their role on the Git provider, and how to configure repository management permissions.
 ---
+import AdminAccessInfo from './../../includes/AdminAccessInfo.astro'
 
 
 By default, Codacy assigns each organization member a role corresponding to that member's role on your Git provider. Each Codacy role, from most restrictive (repository read) to most capable (organization admin), corresponds to a set of permissions that determine what each member can do on Codacy.
@@ -21,8 +22,8 @@ To review the permissions granted by each role, see the tables for each Git prov
 
 To list and manage the members of your Codacy organization, see the [Managing people](managing-people.md) page.
 
-## Configuring repository management permissions {#change-analysis-configuration}
-{% include-markdown "../assets/includes/admin-access-info.md" %}
+## Configuring repository management permissions \{#change-analysis-configuration\}
+<AdminAccessInfo />
 
 By default, only users with the Codacy role **repository write** can change analysis configurations.
 
@@ -40,7 +41,7 @@ To change this, open your organization **Settings**, page **Roles and permission
 
 ## Managing the organization manager role
 
-{% include-markdown "../assets/includes/admin-access-info.md" %}
+<AdminAccessInfo />
 
 To grant an organization member additional permissions, you can assign that member the organization manager role. This role isn't influenced by a member's Git provider role.
 
@@ -404,7 +405,7 @@ The table below maps the GitLab Cloud and GitLab Enterprise roles to the corresp
 
 The table below maps the Bitbucket Cloud and Bitbucket Server roles to the corresponding Codacy roles and the operations that they're allowed to perform:
 
-<table>
+<table class="roles-and-permissions">
   <thead>
     <tr>
       <th>Bitbucket role</th>
@@ -517,36 +518,3 @@ The table below maps the Bitbucket Cloud and Bitbucket Server roles to the corre
 
 -   [Managing people](managing-people.md)
 -   [Accepting new people to your organization](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization)
-
-<!-- vale off -->
-<style>
-/*Center text in all cells except the first column*/
-td:not(:first-child), th:not(:first-child) {
-  text-align: center !important;
-}
-
-/*Background color for row containing the Codacy permission levels*/
-table:not(data-exclude) tr:nth-child(1) td {
-  background-color: #EBF1FF;
-}
-
-/*Add vertical borders and disable horizontal borders*/
-td {
-  border-left: 1px solid var(--md-default-fg-color--lightest);
-  border-top: 1px solid var(--md-default-fg-color--lightest);
-}
-td:nth-child(1) {
-  border-left: 0;
-}
-
-/*Background for cells marking various operations*/
-.yes {
-  background-color: #E6F4EA;
-}
-.no {
-  background-color: #FFF1EB;
-}
-.maybe {
-  background-color: #F2F9FC;
-}
-</style>

…s-configure/codacy-configuration-file.md …-configure/codacy-configuration-file.mdxnew-docs/src/content/docs/repositories-configure/codacy-configuration-file.md renamed to new-docs/src/content/docs/repositories-configure/codacy-configuration-file.mdx new-docs/src/content/docs/repositories-configure/codacy-configuration-file.md renamed to new-docs/src/content/docs/repositories-configure/codacy-configuration-file.mdx

@@ -2,6 +2,7 @@
 title: Codacy configuration file
 description: Use the Codacy configuration file to configure advanced features on Codacy with more control such as ignoring files for duplication or a specific tool, configuring the root directory to start the analysis, and adding custom file extensions to languages.
 ---
+import CoverageIgnore from './../../includes/CoverageIgnore.astro'
 
 
 Codacy supports configuring certain advanced features through a configuration file, such as:
@@ -80,11 +81,11 @@ To use a Codacy configuration file:
     codacy-analysis-cli validate-configuration --directory `pwd`
     ```
 
-## Ignoring files using a Codacy configuration file {#ignore-files}
+## Ignoring files using a Codacy configuration file \{#ignore-files\}
 The Codacy configuration file gives you more flexibility in [ignoring or excluding files](ignoring-files.md) from the Codacy analysis.
 
 :::note
-{% include-markdown "../assets/includes/coverage-ignore.md" %}
+<CoverageIgnore />
 :::
 
 ### Syntax for ignoring files
@@ -126,10 +127,9 @@ engines:
       languages:
         - "typescript"
 ```
-
 :::
 
-## Including specific files using a Codacy configuration file {#include-files}
+## Including specific files using a Codacy configuration file \{#include-files\}
 The Codacy configuration file allows you to explicitly specify files or directories to include in the analysis. This is particularly useful for [bypassing files or directories that are ignored by default](./ignoring-files.md#default-ignored-files) or specified in `exclude_paths`.
 
 :::note
@@ -153,22 +153,22 @@ include_paths:
 
 In this example, while all directories matching `lib*` are excluded, `lib-a` is specifically included for analysis, as well as any files within `libs`.
 
-## Adjusting tool configurations {#tool-conf}
+## Adjusting tool configurations \{#tool-conf\}
 :::note
 The Codacy configuration file lets you [configure tools](#tool-specific-configurations), but you can't enable or disable them. A tool can only be enabled or disabled on the [Code patterns page](configuring-code-patterns.md) by users with the [necessary permissions](../organizations/roles-and-permissions-for-organizations.md).
 :::
 
 ### Which tools can be configured and which name should I use?
 
-<!--NOTE
+{/*<!--NOTE
     When adding a new supported tool, make sure that you update the following pages:
 
     docs/getting-started/supported-languages-and-tools.md
     docs/repositories-configure/local-analysis/client-side-tools.md (if the tool runs client-side)
     docs/organizations/managing-security-and-risk.md  (if the tool reports security issues)
     docs/repositories-configure/configuring-code-patterns.md (supported configuration files table, or list of tools that don't support configuration files)
     docs/repositories-configure/codacy-configuration-file.md (list of tool short names to use on the Codacy configuration file)
--->
+-->*/}
 
 You can use the Codacy configuration file to configure all tools supported by Codacy except the [client-side tools](local-analysis/client-side-tools.md).
 
@@ -273,11 +273,11 @@ If you're using Python 3.4.\* or later as your programming language, disable the
 
 #### PMD CPD (Duplication)
 
-<!--NOTE
+{/*<!--NOTE
     Reference for all options:
 
     https://github.com/codacy/codacy-duplication-pmdcpd/blob/c799cb3a80d1f3b3a8eb9868f63abee13e3e81c4/src/main/scala/com/codacy/duplication/pmd/Cpd.scala#L128
--->
+-->*/}
 
 Codacy uses [PMD's Copy/Paste Detector (CPD)](https://docs.pmd-code.org/latest/) to identify duplicated blocks of code [on the supported languages](../getting-started/supported-languages-and-tools.md).
 
@@ -321,14 +321,14 @@ engines:
     ignoreUsings: false
 ```
 
-## Configuring languages using a Codacy configuration file {#languages}
+## Configuring languages using a Codacy configuration file \{#languages\}
 You can use a Codacy configuration file to manage the languages that Codacy analyzes in your repository.
 
 :::note
 Codacy applies the language settings from the Codacy configuration file as well as any settings defined [in the Codacy UI](languages.md).
 :::
 
-### Adding custom file extensions {#file-extensions}
+### Adding custom file extensions \{#file-extensions\}
 To [add custom file extensions to languages](languages.md#configuring-file-extensions) using a Codacy configuration file, you must define one or more extensions under `languages.<LANGUAGE>.extensions`. Keep in mind that some tools might not work out of the box with those extensions.
 
 For example:
@@ -341,7 +341,7 @@ languages:
       - ".scss"
 ```
 
-### Disabling analysis of a language {#disable-language}
+### Disabling analysis of a language \{#disable-language\}
 To [disable the analysis of a specific language](languages.md#disable-language) using a Codacy configuration file, set `languages.<LANGUAGE>.enabled` to `false`. The analysis is enabled by default for all languages.
 
 For example: