Update links to full docs URLs to skip index

We do not need to link to index files, and in the future
it will be recommended to avoid it.

Changelog: changed

.gitlab/CODEOWNERS

 # When adding a group as a code owner, make sure to invite the group to the
 # project here: https://gitlab.com/gitlab-org/gitlab/-/project_members
-# As described in https://docs.gitlab.com/ee/user/project/codeowners/index.html
+# As described in https://docs.gitlab.com/ee/user/project/codeowners
 
 * @gitlab-org/maintainers/rails-backend @gitlab-org/maintainers/frontend @gitlab-org/maintainers/database @gl-dx/maintainers @gl-dx/tooling-maintainers @gitlab-org/delivery @gitlab-org/maintainers/cicd-templates @gitlab-org/tw-leadership @gitlab-org/maintainers/kas-version-maintainers
 

.gitlab/ci/build-images.gitlab-ci.yml

@@ -12,7 +12,7 @@
 
 # This image is used by:
 # - The `e2e:test-on-omnibus` child pipeline test stage jobs
-# See https://docs.gitlab.com/ee/development/testing_guide/end_to_end/index.html#testing-code-in-merge-requests for more details.
+# See https://docs.gitlab.com/ee/development/testing_guide/end_to_end/#testing-code-in-merge-requests for more details.
 build-qa-image:
   extends:
     - .base-image-build-buildx

.gitlab/ci/release-environments/security.gitlab-ci.yml

@@ -58,7 +58,7 @@ release-environments-update-resource-group:
   stage: prepare
   script:
     # Make sure pipelines run in order
-    # See https://docs.gitlab.com/ee/ci/resource_groups/index.html#change-the-process-mode
+    # See https://docs.gitlab.com/ee/ci/resource_groups/#change-the-process-mode
     - |
       curl --request PUT --data "process_mode=oldest_first" --header "PRIVATE-TOKEN:${ENVIRONMENT_API_TOKEN}" \
       "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/resource_groups/release-environment-${CI_COMMIT_REF_SLUG}"

.gitlab/merge_request_templates/Deprecations.md

@@ -84,7 +84,7 @@ yourself as a reviewer if it's not ready for merge yet.
   - All links must be full URLs, as the deprecation YAML files are used in two different projects. Do not use relative links. The generated doc is an exception to the relative link rule and currently uses absolute links only.
   - Make sure all links and anchors are correct. Do not link to the H1 (top) anchor on a docs page.
 - [ ] Code. Make sure any included code is wrapped in code blocks.
-- [ ] Capitalization. Make sure to capitalize feature names. Stay consistent with the Documentation Style Guidance on [Capitalization](https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#capitalization).
+- [ ] Capitalization. Make sure to capitalize feature names. Stay consistent with the Documentation Style Guidance on [Capitalization](https://docs.gitlab.com/ee/development/documentation/styleguide/#capitalization).
 
 </details>
 

.gitlab/merge_request_templates/Pipeline Configuration.md

@@ -15,7 +15,7 @@
 
 Consider the effect of the changes in this merge request on the following:
 
-- [ ] Different [pipeline types](https://docs.gitlab.com/ee/development/pipelines/index.html#pipelines-types-for-merge-requests)
+- [ ] Different [pipeline types](https://docs.gitlab.com/ee/development/pipelines/#pipelines-types-for-merge-requests)
 - Non-canonical projects:
   - [ ] `gitlab-foss`
   - [ ] `security`

app/graphql/types/query_complexity_type.rb

@@ -14,7 +14,7 @@ class QueryComplexityType < ::Types::BaseObject
       method: :max_complexity,
       see: {
         'GitLab documentation on this limit' =>
-          'https://docs.gitlab.com/ee/api/graphql/index.html#max-query-complexity'
+          'https://docs.gitlab.com/ee/api/graphql/#maximum-query-complexity'
       },
       description: 'GraphQL query complexity limit.'
 

danger/pipeline/Dangerfile

@@ -6,7 +6,7 @@ PIPELINE_CHANGES_MESSAGE = <<~MSG
 This merge request contains changes to the pipeline configuration for the GitLab project.
 
 Please consider the effect of the changes in this merge request on the following:
-- Effects on different [pipeline types](https://docs.gitlab.com/ee/development/pipelines/index.html#pipelines-types-for-merge-requests)
+- Effects on different [pipeline types](https://docs.gitlab.com/ee/development/pipelines/#pipelines-types-for-merge-requests)
 - Effects on non-canonical projects:
   - `gitlab-foss`
   - `security`

doc/api/graphql/reference/_index.md

@@ -35615,7 +35615,7 @@ Pypi metadata.
 | Name | Type | Description |
 | ---- | ---- | ----------- |
-| <a id="querycomplexitylimit"></a>`limit` | [`Int`](#int) | GraphQL query complexity limit. See [GitLab documentation on this limit](https://docs.gitlab.com/ee/api/graphql/index.html#max-query-complexity). |
+| <a id="querycomplexitylimit"></a>`limit` | [`Int`](#int) | GraphQL query complexity limit. See [GitLab documentation on this limit](https://docs.gitlab.com/ee/api/graphql/#maximum-query-complexity). |
 | <a id="querycomplexityscore"></a>`score` | [`Int`](#int) | GraphQL query complexity score. |
 ### `QueueingDelayHistory`

qa/gems/gitlab-cng/README.md

@@ -64,7 +64,7 @@ function cng() {
 
 ### Helm deployment
 
-Because `cng` tool essentially wraps `helm upgrade --install` command, official [Troubleshooting the GitLab chart](https://docs.gitlab.com/charts/troubleshooting/index.html) guide can be used for troubleshooting deployment failures.
+Because `cng` tool essentially wraps `helm upgrade --install` command, official [Troubleshooting the GitLab chart](https://docs.gitlab.com/charts/troubleshooting) guide can be used for troubleshooting deployment failures.
 
 ### CI setup
 

scripts/trigger-build.rb

@@ -256,7 +256,7 @@ def access_token
     %<app_url>s
 
     => For more information, see the documentation
-    => https://docs.gitlab.com/ee/development/documentation/index.html#previewing-the-changes-live
+    => https://docs.gitlab.com/ee/development/documentation/review_apps.html
 
     => If something doesn't work, drop a line in the #docs chat channel.
     MSG

tooling/danger/gitlab_schema_validation_suggestion.rb

@@ -15,7 +15,7 @@ module GitlabSchemaValidationSuggestion
         :warning: You have added `gitlab_main_clusterwide` as the schema for this table. We expect most tables to use the
         `gitlab_main_cell` schema instead, as using the clusterwide schema can have significant scaling implications.
 
-        Please see the [guidelines on choosing gitlab schema](https://docs.gitlab.com/ee/development/cells/index.html#guidelines-on-choosing-between-gitlab_main_cell-and-gitlab_main_clusterwide-schema) for more information.
+        Please see the [guidelines on choosing gitlab schema](https://docs.gitlab.com/ee/development/cells/#choose-either-the-gitlab_main_cell-or-gitlab_main_clusterwide-schema) for more information.
 
         Please consult with `@gitlab-com/gl-infra/tenant-scale/organizations` if you believe that the clusterwide schema is the best fit for this table.
       MESSAGE_MARKDOWN