Add latest changes from gitlab-org/gitlab@master

doc/administration/integration/terminal.md

 # Web terminals
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/7690)
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7690)
 in GitLab 8.15. Only project maintainers and owners can access web terminals.
 With the introduction of the [Kubernetes integration](../../user/project/clusters/index.md),
@@ -92,7 +92,7 @@ they will receive a `Connection failed` message.
 ## Limiting WebSocket connection time
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/8413)
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8413)
 in GitLab 8.17.
 Terminal sessions use long-lived connections; by default, these may last

doc/administration/job_artifacts.md

@@ -77,7 +77,7 @@ _The artifacts are stored by default in
 ### Using object storage
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/1762) in
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1762) in
 >   [GitLab Premium](https://about.gitlab.com/pricing/) 9.4.
 > - Since version 9.5, artifacts are [browsable](../user/project/pipelines/job_artifacts.md#browsing-artifacts),
 >   when object storage is enabled. 9.4 lacks this feature.

doc/administration/job_logs.md

@@ -66,7 +66,7 @@ job output in the UI will be empty.
 ## New incremental logging architecture
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/18169) in GitLab 10.4.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/18169) in GitLab 10.4.
 > - [Announced as generally available](https://gitlab.com/gitlab-org/gitlab-foss/issues/46097) in GitLab 11.0.
 NOTE: **Note:**

doc/administration/lfs/lfs_administration.md

@@ -257,7 +257,7 @@ $ sudo gitlab-rails console            # Login to rails console
 > end
 ```
-See more information in [!19581](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/19581)
+See more information in [!19581](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/19581)
 ## Known limitations
@@ -270,4 +270,4 @@ See more information in [!19581](https://gitlab.com/gitlab-org/gitlab-foss/merge
 [reconfigure gitlab]: ../restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab"
 [restart gitlab]: ../restart_gitlab.md#installations-from-source "How to restart GitLab"
 [eep]: https://about.gitlab.com/pricing/ "GitLab Premium"
-[ee-2760]: https://gitlab.com/gitlab-org/gitlab/merge_requests/2760
+[ee-2760]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/2760

doc/administration/logs.md

@@ -387,7 +387,7 @@ installations from source.
 ## `mail_room_json.log` (default)
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/19186) in GitLab 12.6.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/19186) in GitLab 12.6.
 This file lives in `/var/log/gitlab/mail_room/mail_room_json.log` for
 Omnibus GitLab packages or in `/home/git/gitlab/log/mail_room_json.log` for
@@ -421,7 +421,7 @@ installations from source.
 ## `database_load_balancing.log` **(PREMIUM ONLY)**
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/15442) in GitLab 12.3.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/15442) in GitLab 12.3.
 Contains details of GitLab's [Database Load Balancing](database_load_balancing.md).
 It is stored at:
@@ -450,7 +450,7 @@ etc. For example:
 ## `exceptions_json.log`
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/17819) in GitLab 12.6.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17819) in GitLab 12.6.
 This file lives in
 `/var/log/gitlab/gitlab-rails/exceptions_json.log` for Omnibus GitLab

doc/administration/monitoring/github_imports.md

@@ -98,4 +98,4 @@ The name of the project is stored in the `project` label in the format
 This metric tracks the number of imported repositories across all projects. This
 metric does not expose any labels.
-[14731]: https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/14731
+[14731]: https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/14731

doc/administration/monitoring/prometheus/gitlab_exporter.md

 # GitLab exporter
->- Available since [Omnibus GitLab 8.17](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1132).
->- Renamed from `GitLab monitor exporter` to `GitLab exporter` in [GitLab 12.3](https://gitlab.com/gitlab-org/gitlab/merge_requests/16511).
+>- Available since [Omnibus GitLab 8.17](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1132).
+>- Renamed from `GitLab monitor exporter` to `GitLab exporter` in [GitLab 12.3](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16511).
 The [GitLab exporter](https://gitlab.com/gitlab-org/gitlab-exporter) allows you to
 measure various GitLab metrics, pulled from Redis and the database, in Omnibus GitLab

doc/administration/monitoring/prometheus/gitlab_metrics.md

@@ -17,7 +17,7 @@ GitLab monitors its own internal service metrics, and makes them available at th
 `/-/metrics` endpoint. Unlike other [Prometheus](https://prometheus.io) exporters, in order to access
 it, the client IP needs to be [included in a whitelist](../ip_whitelist.md).
-For Omnibus and Chart installations, these metrics are automatically enabled and collected as of [GitLab 9.4](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1702). For source installations or earlier versions, these metrics will need to be enabled manually and collected by a Prometheus server.
+For Omnibus and Chart installations, these metrics are automatically enabled and collected as of [GitLab 9.4](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1702). For source installations or earlier versions, these metrics will need to be enabled manually and collected by a Prometheus server.
 ## Metrics available

doc/administration/monitoring/prometheus/index.md

@@ -325,5 +325,5 @@ To disable the monitoring of Kubernetes:
 [prometheus]: https://prometheus.io
 [prom-grafana]: https://prometheus.io/docs/visualization/grafana/
 [reconfigure]: ../../restart_gitlab.md#omnibus-gitlab-reconfigure
-[1261]: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1261
+[1261]: https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1261
 [prometheus integration]: ../../../user/project/integrations/prometheus.md

doc/administration/monitoring/prometheus/pgbouncer_exporter.md

@@ -27,7 +27,7 @@ is enabled.
 [← Back to the main Prometheus page](index.md)
-[2493]: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2493
+[2493]: https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/2493
 [PgBouncer exporter]: https://github.com/stanhu/pgbouncer_exporter
 [postgres roles]: https://docs.gitlab.com/omnibus/roles/#postgres-roles
 [prometheus]: https://prometheus.io

doc/administration/monitoring/prometheus/postgres_exporter.md

 # PostgreSQL Server Exporter
 >**Note:**
-Available since [Omnibus GitLab 8.17](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1131).
+Available since [Omnibus GitLab 8.17](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1131).
 For installations from source you will have to install and configure it yourself.
 The [PostgreSQL Server Exporter](https://github.com/wrouesnel/postgres_exporter) allows you to export various PostgreSQL metrics.

doc/administration/monitoring/prometheus/redis_exporter.md

@@ -25,7 +25,7 @@ the Redis exporter exposed under `localhost:9121`.
 [← Back to the main Prometheus page](index.md)
-[1118]: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1118
+[1118]: https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1118
 [redis]: https://redis.io
 [redis exporter]: https://github.com/oliver006/redis_exporter
 [redis-exp]: https://github.com/oliver006/redis_exporter/blob/master/README.md#whats-exported

doc/administration/monitoring/prometheus/registry_exporter.md

 # Registry exporter
-> [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2884) in GitLab 11.9.
+> [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/2884) in GitLab 11.9.
 The Registry exporter allows you to measure various Registry metrics.
 To enable it:

doc/administration/operations/ssh_certificates.md

 # User lookup via OpenSSH's AuthorizedPrincipalsCommand
-> [Available in](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/19911) GitLab
+> [Available in](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/19911) GitLab
 > Community Edition 11.2.
 GitLab's default SSH authentication requires users to upload their SSH

doc/administration/packages/container_registry.md

 # GitLab Container Registry administration
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/4040) in GitLab 8.8.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/4040) in GitLab 8.8.
 > - Container Registry manifest `v1` support was added in GitLab 8.9 to support
 >   Docker versions earlier than 1.10.
@@ -678,7 +678,7 @@ understand the implications.
 ### Removing unused layers not referenced by manifests
-> [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3097) in Omnibus GitLab 11.10.
+> [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/3097) in Omnibus GitLab 11.10.
 DANGER: **Danger:**
 This is a destructive operation.

doc/administration/pages/index.md

@@ -376,7 +376,7 @@ Some GitLab Omnibus upgrades will revert this workaround and you'll need to appl
 ## Activate verbose logging for daemon
-Verbose logging was [introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2533) in
+Verbose logging was [introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/2533) in
 Omnibus GitLab 11.1.
 Follow the steps below to configure verbose logging of GitLab Pages daemon.
@@ -408,7 +408,7 @@ are stored.
 ## Configure listener for reverse proxy requests
-Follow the steps below to configure the proxy listener of GitLab Pages. [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2533) in
+Follow the steps below to configure the proxy listener of GitLab Pages. [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/2533) in
 Omnibus GitLab 11.1.
 1. By default the listener is configured to listen for requests on `localhost:8090`.
@@ -568,8 +568,8 @@ than GitLab to prevent XSS attacks.
 [backup]: ../../raketasks/backup_restore.md
 [ce-14605]: https://gitlab.com/gitlab-org/gitlab-foss/issues/14605
-[ee-80]: https://gitlab.com/gitlab-org/gitlab/merge_requests/80
-[ee-173]: https://gitlab.com/gitlab-org/gitlab/merge_requests/173
+[ee-80]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80
+[ee-173]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/173
 [gitlab pages daemon]: https://gitlab.com/gitlab-org/gitlab-pages
 [NGINX configs]: https://gitlab.com/gitlab-org/gitlab/tree/8-5-stable-ee/lib/support/nginx
 [pages-readme]: https://gitlab.com/gitlab-org/gitlab-pages/blob/master/README.md

doc/administration/pages/source.md

@@ -447,8 +447,8 @@ You should strongly consider running GitLab Pages under a different hostname
 than GitLab to prevent XSS attacks.
 [backup]: ../../raketasks/backup_restore.md
-[ee-80]: https://gitlab.com/gitlab-org/gitlab/merge_requests/80
-[ee-173]: https://gitlab.com/gitlab-org/gitlab/merge_requests/173
+[ee-80]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80
+[ee-173]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/173
 [gitlab pages daemon]: https://gitlab.com/gitlab-org/gitlab-pages
 [NGINX configs]: https://gitlab.com/gitlab-org/gitlab/tree/8-5-stable-ee/lib/support/nginx
 [pages-readme]: https://gitlab.com/gitlab-org/gitlab-pages/blob/master/README.md

doc/administration/pseudonymizer.md

 # Pseudonymizer **(ULTIMATE)**
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/5532) in [GitLab Ultimate][ee] 11.1.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/5532) in [GitLab Ultimate][ee] 11.1.
 As GitLab's database hosts sensitive information, using it unfiltered for analytics
 implies high security requirements. To help alleviate this constraint, the Pseudonymizer

doc/administration/raketasks/github_import.md

 # GitHub import
-> [Introduced]( https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/10308) in GitLab 9.1.
+> [Introduced]( https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10308) in GitLab 9.1.
 In order to retrieve and import GitHub repositories, you will need a
 [GitHub personal access token](https://github.com/settings/tokens).

doc/administration/raketasks/ldap.md

@@ -28,7 +28,7 @@ rake gitlab:ldap:check[50]
 ## Run a Group Sync
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/merge_requests/14735) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.3.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/14735) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.3.
 The following task will run a [group sync](../auth/ldap-ee.md#group-sync) immediately. This is valuable
 when you'd like to update all configured group memberships against LDAP without