Update redirected internal links in code-security (reference (part 1)) (#62153)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: subatoi <32935794+subatoi@users.noreply.github.com>

Author: 4 people

content/code-security/reference/code-quality/codeql-detection.md

@@ -32,12 +32,12 @@ Each {% data variables.product.prodname_code_quality_short %} rule is written as
 
 The rules are continually refined by both {% data variables.product.github %} and open source developers.
 
-* [AUTOTITLE](/code-security/code-quality/reference/codeql-queries/csharp-queries)
-* [AUTOTITLE](/code-security/code-quality/reference/codeql-queries/go-queries)
-* [AUTOTITLE](/code-security/code-quality/reference/codeql-queries/java-queries)
-* [AUTOTITLE](/code-security/code-quality/reference/codeql-queries/javascript-queries)
-* [AUTOTITLE](/code-security/code-quality/reference/codeql-queries/python-queries)
-* [AUTOTITLE](/code-security/code-quality/reference/codeql-queries/ruby-queries)
+* [AUTOTITLE](/code-security/reference/code-quality/codeql-queries/csharp-queries)
+* [AUTOTITLE](/code-security/reference/code-quality/codeql-queries/go-queries)
+* [AUTOTITLE](/code-security/reference/code-quality/codeql-queries/java-queries)
+* [AUTOTITLE](/code-security/reference/code-quality/codeql-queries/javascript-queries)
+* [AUTOTITLE](/code-security/reference/code-quality/codeql-queries/python-queries)
+* [AUTOTITLE](/code-security/reference/code-quality/codeql-queries/ruby-queries)
 
 For more information about the {% data variables.product.prodname_codeql %} project, see [https://codeql.github.com/](https://codeql.github.com).
 
@@ -51,8 +51,8 @@ If your organization has configured caching of private registries, these will be
 
 For more information, see:
 
-* [AUTOTITLE](/code-security/code-quality/how-tos/enable-code-quality)
-* [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries#code-quality-access-to-private-registries)
+* [AUTOTITLE](/code-security/how-tos/maintain-quality-code/enable-code-quality)
+* [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries#code-quality-access-to-private-registries)
 
 ## Pull request status checks
 
@@ -66,4 +66,4 @@ The workflow failed to run. For example, your budget for actions minutes is exha
 
 ### Merging is blocked: Code quality findings were detected
 
-The scan found problems in the code that exceed the quality gate set by a code quality branch rule for the repository. You need to resolve these problems before you can merge the pull request. See [AUTOTITLE](/code-security/code-quality/how-tos/unblock-your-pr).
+The scan found problems in the code that exceed the quality gate set by a code quality branch rule for the repository. You need to resolve these problems before you can merge the pull request. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/unblock-your-pr).

content/code-security/reference/code-quality/metrics-and-ratings.md

@@ -46,4 +46,4 @@ For details about how {% data variables.product.prodname_code_quality_short %} m
 ## Further reading
 
 * [AUTOTITLE](/code-security/concepts/code-quality/code-quality)
-* [AUTOTITLE](/code-security/code-quality/how-tos/interpret-results)
+* [AUTOTITLE](/code-security/how-tos/maintain-quality-code/interpret-results)

content/code-security/reference/code-scanning/code-scanning-logs.md

@@ -11,14 +11,14 @@ category:
   - Find and fix code vulnerabilities
 ---
 
-The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **{% data variables.product.prodname_security_and_quality_tab %}** tab of your repository, by using the **Tool** drop-down menu in the alert list. To access this page, see [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository).
+The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **{% data variables.product.prodname_security_and_quality_tab %}** tab of your repository, by using the **Tool** drop-down menu in the alert list. To access this page, see [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/assess-alerts#viewing-the-alerts-for-a-repository).
 
 ## Logs on {% data variables.product.github %}
 
 You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}.
 
-* Analysis information is shown for the most recent analysis in a header at the top of the list of alerts. See [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository).
-* Diagnostic information is displayed in the {% data variables.product.prodname_actions %} workflow logs and consists of summary metrics and extractor diagnostics. To access these logs, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/viewing-code-scanning-logs).
+* Analysis information is shown for the most recent analysis in a header at the top of the list of alerts. See [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/assess-alerts#viewing-the-alerts-for-a-repository).
+* Diagnostic information is displayed in the {% data variables.product.prodname_actions %} workflow logs and consists of summary metrics and extractor diagnostics. To access these logs, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/view-code-scanning-logs).
 
 ### Summary metrics
 
@@ -28,15 +28,15 @@ You can see analysis and diagnostic information for {% data variables.product.pr
 
 {% data reusables.code-scanning.extractor-diagnostics %}
 
-You can see more detailed information about {% data variables.product.prodname_codeql %} extractor errors and warnings that occurred during database creation by enabling debug logging. See [AUTOTITLE](/code-security/code-scanning/troubleshooting-code-scanning/logs-are-not-detailed-enough#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled).
+You can see more detailed information about {% data variables.product.prodname_codeql %} extractor errors and warnings that occurred during database creation by enabling debug logging. See [AUTOTITLE](/code-security/reference/code-scanning/troubleshoot-analysis-errors/logs-not-detailed-enough#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled).
 
 {% ifversion org-private-registry %}
 
 ### Diagnostic information for private package registries
 
 {% data variables.product.prodname_code_scanning_caps %} default setup workflows include a `Setup proxy for registries` step. When you are looking at a workflow run for default setup, you can expand this step to view the corresponding log. This contains information about which private package registry configurations were available to the analysis. Additionally, the log contains some diagnostic information which may help with troubleshooting if the private package registries are not successfully used by {% data variables.product.prodname_code_scanning %} default setup. Look for the following messages:
 
-* `Using registries_credentials input.` At least one private registry is configured for the organization. This includes configurations for private registry types which are not supported by {% data variables.product.prodname_code_scanning %} default setup. For more details about supported registry types, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries#code-scanning-default-setup-access-to-private-registries).
+* `Using registries_credentials input.` At least one private registry is configured for the organization. This includes configurations for private registry types which are not supported by {% data variables.product.prodname_code_scanning %} default setup. For more details about supported registry types, see [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries#code-scanning-default-setup-access-to-private-registries).
 
 * `Credentials loaded for the following registries:`
   * If no list of configurations follows, then no private registry configurations supported by {% data variables.product.prodname_code_scanning %} default setup were found.
@@ -47,9 +47,9 @@ You can see more detailed information about {% data variables.product.prodname_c
 
 * Following this, there may be messages about the outcomes of connection tests which try to reach the configured private package registries through the authentication proxy. This is a best-effort process. If these checks are not successful for some registries, it does not necessarily mean that the relevant configurations are not working. However, if you find that {% data variables.product.prodname_code_scanning %} default setup is unable to successfully access dependencies in the private registries during the analysis, then this may provide some information to help troubleshoot the issue.
 
-If the output from the `Setup proxy for registries` step is as expected, but {% data variables.product.prodname_code_scanning %} default setup is unable to successfully access dependencies in the private registries, you can obtain additional troubleshooting information. See [AUTOTITLE](/code-security/how-tos/scan-code-for-vulnerabilities/troubleshooting/troubleshooting-analysis-errors/logs-not-detailed-enough#creating-codeql-debugging-artifacts-for-codeql-default-setup).
+If the output from the `Setup proxy for registries` step is as expected, but {% data variables.product.prodname_code_scanning %} default setup is unable to successfully access dependencies in the private registries, you can obtain additional troubleshooting information. See [AUTOTITLE](/code-security/reference/code-scanning/troubleshoot-analysis-errors/logs-not-detailed-enough#creating-codeql-debugging-artifacts-for-codeql-default-setup).
 
-For more information about giving {% data variables.product.prodname_code_scanning %} default setup access to private registries, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries).
+For more information about giving {% data variables.product.prodname_code_scanning %} default setup access to private registries, see [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries).
 
 {% endif %}
 
@@ -63,4 +63,4 @@ Progress and error messages are displayed as notifications in the bottom right c
 
 You can access separate logs for the {% data variables.product.prodname_codeql %} extension, language server, query Server, or tests. The Language Server log contains more advanced debug logs for {% data variables.product.prodname_codeql %} language maintainers. You should only need these to provide details in a bug report.
 
-To access these logs, see [AUTOTITLE](/code-security/how-tos/scan-code-for-vulnerabilities/scan-from-vs-code/accessing-logs).
+To access these logs, see [AUTOTITLE](/code-security/how-tos/find-and-fix-code-vulnerabilities/scan-from-vs-code/accessing-logs).