Changing links to relative following Single Docs Codebase change
As part of merging docs into one Codebase (&199 (closed)), a lot of links were changed to absolute as the MVC way to pass link tests and allow the merge to be relatively painless.
Now that the docs are (mostly) merged, I can start changing those links back to relative. This issue will be used to track the work.
List of docs with full URL occurrences
doc/university/README.md:76:1. [GitLab Training Workshops](https://docs.gitlab.com/ce/university/training/end-user/)
doc/development/documentation/styleguide.md:713:`https://docs.gitlab.com/ce/administration/restart_gitlab.html`.
doc/development/documentation/styleguide.md:965:[gfm]: https://docs.gitlab.com/ce/user/markdown.html#newlines "GitLab flavored markdown documentation"
doc/development/documentation/site_architecture/global_nav.md:257: - `https://docs.gitlab.com/ce/`
doc/development/documentation/site_architecture/global_nav.md:279:For instance, for `https://docs.gitlab.com/ce/user/index.html`,
doc/development/testing_guide/frontend_testing.md:544:[vue-test]: https://docs.gitlab.com/ce/development/fe_guide/vue.html#testing-vue-components
doc/administration/gitaly/index.md:442: 1. Configure [database lookup of SSH keys](https://docs.gitlab.com/ce/administration/operations/fast_ssh_key_lookup.html)
doc/administration/gitaly/index.md:444: 1. Configure [object storage for job artifacts](https://docs.gitlab.com/ce/administration/job_artifacts.html#using-object-storage)
doc/administration/gitaly/index.md:445: including [live tracing](https://docs.gitlab.com/ce/administration/job_traces.html#new-live-trace-architecture).
doc/administration/gitaly/index.md:446: 1. Configure [object storage for LFS objects](https://docs.gitlab.com/ce/workflow/lfs/lfs_administration.html#storing-lfs-objects-in-remote-object-storage).
doc/administration/gitaly/index.md:447: 1. Configure [object storage for uploads](https://docs.gitlab.com/ce/administration/uploads.html#using-object-storage-core-only).
doc/install/google_cloud_platform/index.md:131:- [Integration documentation](https://docs.gitlab.com/ce/integration/)
doc/install/google_cloud_platform/index.md:132:- [GitLab Pages configuration](https://docs.gitlab.com/ce/administration/pages/index.html)
doc/install/google_cloud_platform/index.md:133:- [GitLab Container Registry configuration](https://docs.gitlab.com/ce/administration/container_registry.html)
doc/install/azure/index.md:423:[GitLab-Docs]: https://docs.gitlab.com/ce/README.html "GitLab Documentation"
doc/install/azure/index.md:424:[GitLab-Technical-Articles]: https://docs.gitlab.com/ce/articles/index.html "GitLab Technical Articles"
doc/install/azure/index.md:425:[GitLab-Docs-SSH]: https://docs.gitlab.com/ce/ssh/README.html "GitLab Documentation: SSH"
doc/user/project/pages/getting_started_part_four.md:383:[documentation of GitLab CI](https://docs.gitlab.com/ce/ci/yaml/README.html)
doc/user/project/integrations/webhooks.md:27:We already have a [built-in receiver](https://docs.gitlab.com/ce/project_services/slack.html)
doc/development/changelog.md:38:- Any change behind a feature flag **should not** have a changelog entry. The entry should be added [in the merge request removing the feature flags](https://docs.gitlab.com/ee/development/feature_flags.html#developing-with-feature-flags).
doc/development/documentation/structure.md:43:<!--Follow the Style Guide when working on this document. https://docs.gitlab.com/ee/development/documentation/styleguide.html
doc/development/documentation/index.md:180:It supports both full and relative URLs, e.g. `https://docs.gitlab.com/ee/path/to/file.html`, `../path/to/file.html`, `path/to/file.md`. Note that any `*.md` paths will be compiled to `*.html`.
doc/development/documentation/styleguide.md:387:For more information, see the [confidential issue](https://docs.gitlab.com/ee/user/project/issues/confidential_issues.html) `https://gitlab.com/gitlab-org/gitlab-ce/issues/<issue_number>`.
doc/development/documentation/site_architecture/global_nav.md:218: - For `https://docs.gitlab.com/ee/README.html`, the relative URL is `README.html`.
doc/development/documentation/site_architecture/global_nav.md:219: - For `https://docs.gitlab.com/ee/user/project/cycle_analytics.html`, the relative
doc/development/documentation/site_architecture/global_nav.md:258: - `https://docs.gitlab.com/ee/`
doc/development/documentation/site_architecture/global_nav.md:264: - `https://docs.gitlab.com/ee/user/group/epics/`
doc/development/documentation/site_architecture/global_nav.md:265: - `https://docs.gitlab.com/ee/user/project/security_dashboard.html`
doc/development/documentation/site_architecture/global_nav.md:286:`https://docs.gitlab.com/ee/`, thus, all links
doc/development/testing_guide/end_to_end/quick_start_guide.md:389:> This `GET` path can be found in the [public API documentation](https://docs.gitlab.com/ee/api/issues.html#single-issue).
doc/development/testing_guide/end_to_end/quick_start_guide.md:393:> This `POST` path can be found in the [public API documentation](https://docs.gitlab.com/ee/api/issues.html#new-issue).
doc/development/testing_guide/end_to_end/quick_start_guide.md:397:> Notice that we pass both `labels` and `title` attributes in the `api_post_body`, where `labels` receives an array of labels, and [`title` is required](https://docs.gitlab.com/ee/api/issues.html#new-issue). Also, notice that we keep them alphabetically organized.
doc/development/testing_guide/end_to_end/quick_start_guide.md:436:> Notice that we pass both `color` and `name` attributes in the `api_post_body` since [those are required](https://docs.gitlab.com/ee/api/labels.html#create-a-new-label). Also, notice that we keep them alphabetically organized.
doc/development/chatops_on_gitlabcom.md:19: - [Chatops Usage](https://docs.gitlab.com/ee/ci/chatops/README.html)
doc/integration/README.md:74:[jenkins]: https://docs.gitlab.com/ee/integration/jenkins.html
doc/administration/logs.md:7:documentation](https://docs.gitlab.com/ee/administration/audit_events.html)
doc/workflow/repository_mirroring.md:289:afterwards. If you notify GitLab by [API](https://docs.gitlab.com/ee/api/projects.html#start-the-pull-mirroring-process-for-a-project-starter),
doc/workflow/repository_mirroring.md:292:For more information, see [Start the pull mirroring process for a Project](https://docs.gitlab.com/ee/api/projects.html#start-the-pull-mirroring-process-for-a-project-starter).
doc/ci/examples/code_quality.md:2:redirect_from: 'https://docs.gitlab.com/ee/ci/examples/code_climate.html'
doc/ci/examples/laravel_with_gitlab_and_envoy/index.md:2:redirect_from: 'https://docs.gitlab.com/ee/articles/laravel_with_gitlab_and_envoy/index.html'
doc/ci/examples/artifactory_and_gitlab/index.md:2:redirect_from: 'https://docs.gitlab.com/ee/articles/artifactory_and_gitlab/index.html'
doc/ci/docker/using_docker_build.md:147: # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services
doc/ci/ci_cd_for_external_repos/github_integration.md:112: [trigger pull mirroring](https://docs.gitlab.com/ee/api/projects.html#start-the-pull-mirroring-process-for-a-project-starter),
doc/README.md:7: <em>Visit <a href="https://docs.gitlab.com/ee/">docs.gitlab.com</a> for optimized
doc/user/project/issues/moving_issues.md:18:To access rails console run `sudo gitlab-rails console` on the GitLab server and run the below script. Please be sure to change **project**, **admin_user** and **target_project** to your values. We do also recommend [creating a backup](https://docs.gitlab.com/ee/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system) before attempting any changes in the console.
doc/user/project/protected_branches.md:183:[ee-restrict]: https://docs.gitlab.com/ee/user/project/protected_branches.html#restricting-push-and-merge-access-to-certain-users
doc/user/application_security/container_scanning/index.md:125: ## https://docs.gitlab.com/ee/ci/variables/README.html#predefined-environment-variables
doc/user/application_security/container_scanning/index.md:168: ## https://docs.gitlab.com/ee/ci/variables/README.html#predefined-environment-variables
doc/topics/application_development_platform/index.md:29:[Auto DevOps](https://docs.gitlab.com/ee/topics/autodevops/) to provide those workflows. Auto DevOps works with
doc/topics/application_development_platform/index.md:31:an incremental consumption path. Because it is [composable](https://docs.gitlab.com/ee/topics/autodevops/#using-components-of-auto-devops),
doc/topics/application_development_platform/index.md:41:- [Auto SAST (Static Application Security Testing)](https://docs.gitlab.com/ee/topics/autodevops/#auto-sast-ultimate)
doc/topics/application_development_platform/index.md:42:- [Auto Dependency Scanning](https://docs.gitlab.com/ee/topics/autodevops/#auto-dependency-scanning-ultimate)
doc/topics/application_development_platform/index.md:43:- [Auto Container Scanning](https://docs.gitlab.com/ee/topics/autodevops/#auto-container-scanning-ultimate)
doc/topics/application_development_platform/index.md:44:- [Auto DAST (Dynamic Application Security Testing)](https://docs.gitlab.com/ee/topics/autodevops/#auto-dast-ultimate)
doc/topics/application_development_platform/index.md:52:- [Auto Monitoring](https://docs.gitlab.com/ee/topics/autodevops/#auto-monitoring)
doc/topics/application_development_platform/index.md:53:- [In-app Kubernetes Pod Logs](https://docs.gitlab.com/ee/user/project/clusters/kubernetes_pod_logs.html)
Edited by Achilleas Pipinellis