moved all Id attributes to new format

Author: claudiacodacy

new-docs/src/content/docs/coverage-reporter/alternative-ways-of-running-coverage-reporter.md

@@ -10,8 +10,7 @@ The following sections list the alternative ways of running or installing Codacy
 **If you're using Codacy Self-hosted {{ extra.codacy_self_hosted_version }}** you must use [Codacy Coverage Reporter {{ extra.codacy_coverage_reporter_version }}](https://github.com/codacy/codacy-coverage-reporter/releases/tag/{{ extra.codacy_coverage_reporter_version }}) to ensure it's compatible with your Codacy instance.
 :::
 
-## Bash script (recommended) {: id="bash-script"}
-
+## Bash script (recommended) {#bash-script}
 The recommended way to run the Codacy Coverage Reporter is by using the [self-contained bash script `get.sh`](https://github.com/codacy/codacy-coverage-reporter/blob/master/get.sh) that automatically downloads and runs the most recent version of the Codacy Coverage Reporter:
 
 -   On Ubuntu, run:

new-docs/src/content/docs/coverage-reporter/index.md

@@ -24,8 +24,7 @@ Complete these main steps to set up coverage for your repository:
 
 The next sections include detailed instructions on how to complete each step of the setup process.
 
-## 1. Generating coverage reports {: id="generating-coverage"}
-
+## 1. Generating coverage reports {#generating-coverage}
 Before setting up Codacy to display code coverage metrics for your repository you must have tests and use tools to generate coverage reports for the source code files in your repository.
 
 Consider the following when generating coverage reports for your repository:
@@ -142,8 +141,7 @@ As a last resort, you can also send the coverage data directly by calling one of
 -   [<span class="skip-vale">saveCoverage</span>](https://api.codacy.com/swagger#savecoverage)
 -   [saveCoverageWithAccountToken](https://api.codacy.com/swagger#savecoveragewithaccounttoken)
 
-## 2. Uploading coverage data to Codacy {: id="uploading-coverage"}
-
+## 2. Uploading coverage data to Codacy {#uploading-coverage}
 After having coverage reports set up for your repository, you must use the Codacy Coverage Reporter to upload them to Codacy. The recommended way to do this is by using a CI/CD platform that automatically runs tests, generates coverage, and then uses the Codacy Coverage Reporter to upload the coverage report information to Codacy.
 
 :::caution
@@ -161,9 +159,7 @@ However, the instructions on this page assume that you'll run the recommended [s
 
 :::
 
-1.  Set up an API token to allow Codacy Coverage Reporter to authenticate on Codacy:
-    {: id="authenticate"}
-
+1.  Set up an API token to allow Codacy Coverage Reporter to authenticate on Codacy: {#authenticate}
     -   **If you're setting up coverage for one repository**, [obtain a repository API token](../codacy-api/api-tokens.md#repository-api-tokens) and set the following environment variable to specify your repository API token:
 
         ```bash
@@ -214,8 +210,7 @@ However, the instructions on this page assume that you'll run the recommended [s
     Be sure to also check the [instructions for more advanced scenarios](uploading-coverage-in-advanced-scenarios.md) while uploading the coverage data to Codacy, such as when running parallel tests, using monorepos, or testing source code in multiple or unsupported languages.
     :::
 
-## 3. Validating that the coverage setup is complete {: id="validating-coverage"}
-
+## 3. Validating that the coverage setup is complete {#validating-coverage}
 Codacy displays the code coverage in each branch, as well as the evolution of code coverage between commits and the code coverage variation introduced by pull requests.
 
 Because of this, to ensure that all code coverage metrics are available on Codacy, you must have successfully uploaded coverage data and analyzed:
@@ -246,8 +241,7 @@ Follow these instructions to validate that your coverage setup is working correc
 
     If there are commits with a status different from **Processed**, please follow the troubleshooting instructions for the corresponding error status and click the button **Test integration** to display any new coverage reports uploaded to Codacy.
 
-    ### Commit not found {: id="status-commit-not-found" style="color: #EF5454;"}
-
+    ### Commit not found {#status-commit-not-found}
     Codacy doesn't have information about the commit associated with the coverage data.
 
     <table>
@@ -281,8 +275,7 @@ Follow these instructions to validate that your coverage setup is working correc
     </tr>
     </table>
 
-    ### Branch not enabled {: id="status-branch-not-enabled" style="color: #EF5454;"}
-
+    ### Branch not enabled {#status-branch-not-enabled}
     The commit associated with the coverage data doesn't belong to any branch that Codacy is analyzing.
 
     <table>
@@ -316,8 +309,7 @@ Follow these instructions to validate that your coverage setup is working correc
     </tr>
     </table>
 
-    ### Commit not analyzed {: id="status-commit-not-analyzed" style="color: #EF5454;"}
-
+    ### Commit not analyzed {#status-commit-not-analyzed}
     Due to technical limitations, Codacy only reports coverage for a commit after successfully completing the static code analysis of that commit.
 
     <table>
@@ -374,8 +366,7 @@ Follow these instructions to validate that your coverage setup is working correc
     </tr>
     </table>
 
-    ### Final report not sent {: id="status-final-report-not-sent" style="color: #EF5454;"}
-
+    ### Final report not sent {#status-final-report-not-sent}
     Codacy is waiting to receive more coverage data before reporting the coverage for a commit.
 
     <table>
@@ -400,8 +391,7 @@ Follow these instructions to validate that your coverage setup is working correc
     </tr>
     </table>
 
-    ### Pending {: id="status-pending" style="color: #2562EA;"}
-
+    ### Pending {#status-pending}
     Codacy is waiting to receive valid coverage data for the files in your repository.
 
     <table>

new-docs/src/content/docs/coverage-reporter/troubleshooting-coverage-cli-issues.md

@@ -27,8 +27,7 @@ However, if Codacy Coverage Reporter doesn't find your coverage report, you can
 bash <(curl -Ls https://coverage.codacy.com/get.sh) report -r <coverage report file name>
 ```
 
-## Can't validate checksum {: id="checksum"}
-
+## Can't validate checksum {#checksum}
 Starting on version [13.0.0](https://github.com/codacy/codacy-coverage-reporter/releases/tag/13.0.0) the `get.sh` script automatically validates the checksum of the downloaded Codacy Coverage Reporter binary. This requires having either the `sha512sum` or `shasum` command on the operating system where you're running the script.
 
 If you're getting this error while uploading your coverage data to Codacy, install the correct version of `sha512sum` or `shasum` for the operating system that you're using.
@@ -39,8 +38,7 @@ You can also skip validating the checksum of the binary by defining the followin
 export CODACY_REPORTER_SKIP_CHECKSUM=true
 ```
 
-## Commit SHA-1 hash detection {: id="commit-detection"}
-
+## Commit SHA-1 hash detection {#commit-detection}
 The Codacy Coverage Reporter automatically detects the SHA-1 hash of the current commit to associate with the coverage data when you're using one of the following CI/CD platforms:
 
 -   <span class="skip-vale">Appveyor</span>
@@ -130,8 +128,7 @@ Make sure that your coverage report isn't empty and that it includes coverage da
 If you upload multiple coverage reports and at least one contains valid data, the Codacy Coverage Reporter uploads the valid reports and ignores the invalid ones.
 :::
 
-## Report generated an empty result while uploading C# coverage data {: id="detailedxml"}
-
+## Report generated an empty result while uploading C# coverage data {#detailedxml}
 If you're using <span class="skip-vale">dotCover</span> to generate coverage reports for your C# projects, you must use the <span class="skip-vale">dotCover</span> detailedXML report format as follows:
 
 ```bash

new-docs/src/content/docs/coverage-reporter/uploading-coverage-in-advanced-scenarios.md

@@ -6,8 +6,7 @@ description: Instructions on how to use the Codacy Coverage Reporter to upload c
 
 The following sections include instructions on how to use the Codacy Coverage Reporter to upload coverage data in more advanced scenarios.
 
-## Uploading multiple coverage reports for the same language {: id="multiple-reports"}
-
+## Uploading multiple coverage reports for the same language {#multiple-reports}
 If your test suite is split into different modules or runs in parallel, you must upload multiple coverage reports for the same language either at once or in sequence.
 
 Alternatively, consider merging multiple coverage reports before uploading them to Codacy. Most coverage tools support merging or aggregating coverage data. For example, use the [merge mojo for JaCoCo](http://www.eclemma.org/jacoco/trunk/doc/merge-mojo.html).
@@ -16,8 +15,7 @@ Alternatively, consider merging multiple coverage reports before uploading them
 If one or more coverage reports mark a line as covered multiple times, Codacy counts it as a single covered line when calculating coverage.
 :::
 
-### Uploading all reports at once {: id="multiple-reports-once"}
-
+### Uploading all reports at once {#multiple-reports-once}
 Upload multiple partial coverage reports with a single command by specifying each report with the flag `-r`. For example:
 
 ```bash
@@ -32,8 +30,7 @@ bash <(curl -Ls https://coverage.codacy.com/get.sh) report \
     -l Java $(find . -name 'jacoco*.xml' | sed 's,^, -r ,' | xargs echo)
 ```
 
-### Uploading reports in sequence {: id="multiple-reports-sequence"}
-
+### Uploading reports in sequence {#multiple-reports-sequence}
 Upload multiple partial coverage reports in sequence:
 
 1.  Upload each report <span class="skip-vale">separately</span> with the flag `--partial`.
@@ -52,8 +49,7 @@ bash <(curl -Ls https://coverage.codacy.com/get.sh) report \
 bash <(curl -Ls https://coverage.codacy.com/get.sh) final
 ```
 
-## Uploading the same coverage report for multiple languages {: id="multiple-languages"}
-
+## Uploading the same coverage report for multiple languages {#multiple-languages}
 If your test suite generates a single coverage report for more than one language, you must upload the same coverage report for each language.
 
 To do this, upload the same report multiple times, specifying each different language with the flag `-l`. For example:
@@ -66,8 +62,7 @@ bash <(curl -Ls https://coverage.codacy.com/get.sh) report \
 bash <(curl -Ls https://coverage.codacy.com/get.sh) final
 ```
 
-## Uploading coverage for Golang {: id="golang"}
-
+## Uploading coverage for Golang {#golang}
 Codacy can't automatically detect Golang coverage report files because they don't have specific file names.
 
 If you're uploading a Golang coverage report, you must also specify the report type:
@@ -78,8 +73,7 @@ bash <(curl -Ls https://coverage.codacy.com/get.sh) report \
     --force-coverage-parser go -r unit.coverage.out
 ```
 
-## Uploading coverage for unsupported languages {: id="unsupported-languages"}
-
+## Uploading coverage for unsupported languages {#unsupported-languages}
 If your language isn't in the [list of supported languages](index.md#generating-coverage), you can still send coverage to Codacy.
 
 To do this, provide the correct language with the flag `-l`, together with `--force-language`. For example:

new-docs/src/content/docs/faq/troubleshooting/why-did-codacy-stop-commenting-on-pull-requests.md

@@ -12,8 +12,7 @@ Coverage information is currently sent to GitHub by a new version of the Codacy
 
 If you stopped receiving coverage summaries on your pull requests, please [review and accept the updated Codacy app permissions on GitHub](https://docs.github.com/en/enterprise-cloud@latest/apps/using-github-apps/reviewing-and-modifying-installed-github-apps#reviewing-permissions). For more information on the rollout of the new Coverage engine, [see the relevant release note](../../release-notes/cloud/cloud-2023-11-23-new-coverage-engine-status-checks.md).
 
-## Outdated permissions or invalid SSH key {: id="outdated-permissions"}
-
+## Outdated permissions or invalid SSH key {#outdated-permissions}
 :::note[This section applies to GitLab and Bitbucket]
 :::
 

new-docs/src/content/docs/getting-started/configuring-your-repository.md

@@ -23,8 +23,7 @@ To configure your repository, follow these steps:
 
 ![Ignoring files](../repositories-configure/images/ignored-files.png)
 
-## 2. Configuring code patterns {: id="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
@@ -33,16 +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) {: id="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 {: id="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

new-docs/src/content/docs/getting-started/integrating-codacy-with-your-git-workflow.md

@@ -17,8 +17,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 {: id="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
@@ -38,8 +37,7 @@ 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 {: id="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)).
 
 {%
@@ -50,8 +48,7 @@ Make sure you enable the option **Status checks** ([GitHub](../repositories-conf
 
 ![Enabling your Git provider integration](../repositories-configure/integrations/images/github-integration.png)
 
-## 3. Blocking merging pull requests (optional) {: id="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

new-docs/src/content/docs/organizations/integrations/default-git-provider-integration-settings.md

@@ -11,8 +11,7 @@ To configure these default settings, open your organization **Integrations** pag
 
 The organization-level Git provider integration settings define the defaults that Codacy applies to new repositories. You can then customize the settings for each individual repository, which depend on your Git provider, [GitHub](../../repositories-configure/integrations/github-integration.md), [GitLab](../../repositories-configure/integrations/gitlab-integration.md) or [Bitbucket](../../repositories-configure/integrations/bitbucket-integration.md).
 
-## Applying default settings to all repositories {: id="apply-all"}
-
+## Applying default settings to all repositories {#apply-all}
 To ensure that all your repositories are configured with the default Git provider integration settings defined for your organization, click the button **Apply default to all repositories**.
 
 ![Apply default settings to all repositories](images/default-git-provider-settings-apply-all.png)

new-docs/src/content/docs/organizations/managing-people.md

@@ -23,8 +23,7 @@ To list and manage the people in your organization, open your organization **Set
 
 ![People in an organization](images/organization-people.png)
 
-## Joining an organization {: id="joining"}
-
+## Joining an organization {#joining}
 To become a member of an organization on Codacy app you must [sign up to Codacy](../getting-started/codacy-quickstart.md) using your Git provider and follow the instructions to either join an existing organization or add a new one.
 
 To join or add an organization after completing the sign-up process, click **Organizations** on the top right-hand menu under your avatar:
@@ -35,8 +34,7 @@ To join or add an organization after completing the sign-up process, click **Org
 **On Codacy Cloud**, organization admins [control if team members need an approval](changing-your-plan-and-billing.md#allowing-new-people-to-join-your-organization) before joining their organizations.
 :::
 
-## Adding people to your organization {: id="adding-people"}
-
+## Adding people to your organization {#adding-people}
 **On Codacy Cloud**, organization admins can also add teammates to their organization on Codacy. This is useful to allow Codacy to analyze commits to private repositories by committers who haven't signed up to Codacy or joined the organization yet.
 
 :::tip
@@ -68,8 +66,7 @@ To add people to your organization:
 
 1.  Confirm the updated billing details displayed at the bottom of the window and click the button **Add people**. Codacy emails the newly added people inviting them to log in.
 
-## Removing people from your organization {: id="removing-people"}
-
+## Removing people from your organization {#removing-people}
 Members of an organization on Codacy can remove themselves from the organization, and organization admins can also remove other members and committers.
 
 When a member or committer leaves an organization:

new-docs/src/content/docs/organizations/managing-repositories.md

@@ -27,8 +27,7 @@ The list also displays error and warning messages for repositories that have iss
 
 If you follow many repositories, you can use the search field above the list to <span class="skip-vale">quickly</span> find a specific repository.
 
-## Adding a repository {: id="adding-a-repository"}
-
+## Adding a repository {#adding-a-repository}
 {%
     include-markdown "../assets/includes/paid.md"
     start="<!--paid-private-repositories-start-->"
@@ -55,8 +54,7 @@ Although Codacy immediately starts analyzing newly added repositories, they disp
 
 ![Waiting for first analysis results](images/repositories-analyzing.png)
 
-## Following or unfollowing a repository {: id="follow-unfollow"}
-
+## Following or unfollowing a repository {#follow-unfollow}
 Users with [no permission to add a repository](roles-and-permissions-for-organizations.md) to Codacy, can follow that repository after it has been added to Codacy, and stop following it at any time.
 
 To follow or unfollow repositories on Codacy:
@@ -76,8 +74,7 @@ Conversely, you automatically **stop following** a repository as soon as you try
 
 :::
 
-## Finding your repositories with Segments {: id="provider-segments"}
-
+## Finding your repositories with Segments {#provider-segments}
 Codacy allows you to utilise [**Segments**](../segments) to categorize and filter repositories more effectively within the Codacy platform.
 :::note[Check out how to [enable and configure **Segments**](../segments/#enabling-segments)]
 :::