Add latest changes from gitlab-org/gitlab@master

20 files changed, 239 insertions, 26 deletions

diff --git a/doc/administration/auth/ldap/index.md b/doc/administration/auth/ldap/index.md
index 7687f7c9340..cdd6926268a 100644
--- a/doc/administration/auth/ldap/index.md
+++ b/doc/administration/auth/ldap/index.md
@@ -1047,7 +1047,7 @@ For more information on synchronizing users and groups between LDAP and GitLab,
 1. In the configuration file, change:
    - `omniauth_auto_link_user` to `saml` only.
    - `omniauth_auto_link_ldap_user` to false.
-   - `ldap_enabled` to `false`. 
+   - `ldap_enabled` to `false`.
    You can also comment out the LDAP provider settings.
 
 ## Troubleshooting
diff --git a/doc/administration/docs_self_host.md b/doc/administration/docs_self_host.md
index d1ad36880dd..e4cb1898aae 100644
--- a/doc/administration/docs_self_host.md
+++ b/doc/administration/docs_self_host.md
@@ -84,7 +84,7 @@ You can use GitLab Pages to host the GitLab product documentation.
 
 Prerequisite:
 
-- Ensure the Pages site URL does not use a subfolder. Because of the way the                       
+- Ensure the Pages site URL does not use a subfolder. Because of the way the
   site is pre-compiled, the CSS and JavaScript files are relative to the
   main domain or subdomain. For example, URLs like `https://example.com/docs/`
   are not supported.
diff --git a/doc/administration/geo/setup/index.md b/doc/administration/geo/setup/index.md
index eef915bb5d8..3525199226d 100644
--- a/doc/administration/geo/setup/index.md
+++ b/doc/administration/geo/setup/index.md
@@ -35,7 +35,7 @@ If both Geo sites are based on the [1K reference architecture](../../reference_a
 1. Optional: [Configure a secondary LDAP server](../../auth/ldap/index.md) for the **secondary** sites. See [notes on LDAP](../index.md#ldap).
 1. Optional: [Configure Geo secondary proxying](../secondary_proxy/index.md) to use a single, unified URL for all Geo sites. This step is recommended to accelerate most read requests while transparently proxying writes to the primary Geo site.
 1. Follow the [Using a Geo Site](../replication/usage.md) guide.
- 
+
 ### Multi-node Geo sites
 
 If one or more of your sites is using the [2K reference architecture](../../reference_architectures/2k_users.md) or larger, see
diff --git a/doc/administration/monitoring/prometheus/gitlab_metrics.md b/doc/administration/monitoring/prometheus/gitlab_metrics.md
index f8cab0c605e..772b10ed863 100644
--- a/doc/administration/monitoring/prometheus/gitlab_metrics.md
+++ b/doc/administration/monitoring/prometheus/gitlab_metrics.md
@@ -204,6 +204,7 @@ configuration option in `gitlab.yml`. These metrics are served from the
 | `sidekiq_jobs_dead_total`                      | Counter   | 13.7 | Sidekiq dead jobs (jobs that have run out of retries)                                               | `queue`, `boundary`, `external_dependencies`, `feature_category`, `urgency` |
 | `sidekiq_redis_requests_total`                 | Counter   | 13.1 | Redis requests during a Sidekiq job execution                                                       | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
 | `sidekiq_elasticsearch_requests_total`         | Counter   | 13.1 | Elasticsearch requests during a Sidekiq job execution                                                       | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
+| `sidekiq_jobs_deferred_total`                  | Counter   | 16.1 | Number of jobs being deferred when `defer_sidekiq_jobs` feature flag is enabled                       | `worker`                                                                                   |
 | `sidekiq_running_jobs`                         | Gauge     | 12.2 | Number of Sidekiq jobs running                                                                      | `queue`, `boundary`, `external_dependencies`, `feature_category`, `urgency` |
 | `sidekiq_concurrency`                          | Gauge     | 12.5 | Maximum number of Sidekiq jobs                                                                      |                                                                   |
 | `sidekiq_mem_total_bytes`                      | Gauge     | 15.3 | Number of bytes allocated for both objects consuming an object slot and objects that required a malloc'|                                                                   |
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index 4bed7bcd634..1578b5bd328 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -12403,6 +12403,7 @@ Represents the total number of issues and their weights for a particular day.
 | <a id="cicatalogresourceicon"></a>`icon` **{warning-solid}** | [`String`](#string) | **Introduced** in 15.11. This feature is an Experiment. It can be changed or removed at any time. Icon for the catalog resource. |
 | <a id="cicatalogresourceid"></a>`id` **{warning-solid}** | [`ID!`](#id) | **Introduced** in 15.11. This feature is an Experiment. It can be changed or removed at any time. ID of the catalog resource. |
 | <a id="cicatalogresourcename"></a>`name` **{warning-solid}** | [`String`](#string) | **Introduced** in 15.11. This feature is an Experiment. It can be changed or removed at any time. Name of the catalog resource. |
+| <a id="cicatalogresourcewebpath"></a>`webPath` **{warning-solid}** | [`String`](#string) | **Introduced** in 16.1. This feature is an Experiment. It can be changed or removed at any time. Web path of the catalog resource. |
 
 #### Fields with arguments
 
@@ -18648,6 +18649,7 @@ Represents the network policy.
 | Name | Type | Description |
 | ---- | ---- | ----------- |
 | <a id="noteauthor"></a>`author` | [`UserCore!`](#usercore) | User who wrote this note. |
+| <a id="noteawardemoji"></a>`awardEmoji` | [`AwardEmojiConnection`](#awardemojiconnection) | List of award emojis associated with the note. (see [Connections](#connections)) |
 | <a id="notebody"></a>`body` | [`String!`](#string) | Content of the note. |
 | <a id="notebodyhtml"></a>`bodyHtml` | [`String`](#string) | GitLab Flavored Markdown rendering of `note`. |
 | <a id="noteconfidential"></a>`confidential` **{warning-solid}** | [`Boolean`](#boolean) | **Deprecated** in 15.5. This was renamed. Use: `internal`. |
diff --git a/doc/api/namespaces.md b/doc/api/namespaces.md
index 15ce73fdbc3..ddf56209be2 100644
--- a/doc/api/namespaces.md
+++ b/doc/api/namespaces.md
@@ -54,7 +54,8 @@ Example response:
     "billable_members_count": 1,
     "plan": "default",
     "trial_ends_on": null,
-    "trial": false
+    "trial": false,
+    "root_repository_size": 100
   },
   {
     "id": 2,
@@ -69,7 +70,8 @@ Example response:
     "billable_members_count": 2,
     "plan": "default",
     "trial_ends_on": null,
-    "trial": false
+    "trial": false,
+    "root_repository_size": 100
   },
   {
     "id": 3,
@@ -84,7 +86,8 @@ Example response:
     "billable_members_count": 5,
     "plan": "default",
     "trial_ends_on": null,
-    "trial": false
+    "trial": false,
+    "root_repository_size": 100
   }
 ]
 ```
@@ -124,7 +127,7 @@ once a day.
 ```
 
 NOTE:
-Only group owners are presented with `members_count_with_descendants` and `plan`.
+Only group owners are presented with `members_count_with_descendants`, `root_repository_size` and `plan`.
 
 ## Get namespace by ID
 
@@ -162,7 +165,8 @@ Example response:
   "seats_in_use": 0,
   "plan": "default",
   "trial_ends_on": null,
-  "trial": false
+  "trial": false,
+  "root_repository_size": 100
 }
 ```
 
@@ -190,7 +194,8 @@ Example response:
   "seats_in_use": 0,
   "plan": "default",
   "trial_ends_on": null,
-  "trial": false
+  "trial": false,
+  "root_repository_size": 100
 }
 ```
 
diff --git a/doc/architecture/blueprints/cells/index.md b/doc/architecture/blueprints/cells/index.md
index 9938875adb6..94ff12f2c55 100644
--- a/doc/architecture/blueprints/cells/index.md
+++ b/doc/architecture/blueprints/cells/index.md
@@ -119,7 +119,7 @@ would be required to define a general split of data and build required tooling.
 
 1. **User can push to Git repository.**
 
-    The purpose is to ensure that essential joins from the projects table are properly attributed to be 
+    The purpose is to ensure that essential joins from the projects table are properly attributed to be
     Cell-local, and as a result the essential Git workflow is supported.
 
 1. **User can run CI pipeline.**
@@ -159,7 +159,7 @@ This list is not exhaustive of work needed to be done.
 ### 4. Routing layer
 
 The routing layer is meant to offer a consistent user experience where all Cells are presented
-under a single domain (for example, `gitlab.com`), instead of 
+under a single domain (for example, `gitlab.com`), instead of
 having to navigate to separate domains.
 
 The user will able to use `https://gitlab.com` to access Cell-enabled GitLab. Depending
diff --git a/doc/architecture/blueprints/organization/index.md b/doc/architecture/blueprints/organization/index.md
index 8eb367ddfc8..bebd1be593a 100644
--- a/doc/architecture/blueprints/organization/index.md
+++ b/doc/architecture/blueprints/organization/index.md
@@ -87,14 +87,14 @@ Self-managed instances would set a default Organization.
 
 The Organization MVC will contain the following functionality:
 
-- Instance setting to allow the creation of multiple Organizations. This will be enabled by default on GitLab.com, and disabled for self-managed GitLab. 
+- Instance setting to allow the creation of multiple Organizations. This will be enabled by default on GitLab.com, and disabled for self-managed GitLab.
 - Every instance will have a default organization. Initially, all users will be managed by this default Organization.
 - Organization Owner. The creation of an Organization appoints that user as the Organization Owner. Once established, the Organization Owner can appoint other Organization Owners.
 - Organization users. A user is managed by one Organization, but can be part of multiple Organizations. Users are able to navigate between the different Organizations they are part of.
 - Setup settings. Containing the Organization name, ID, description, README, and avatar. Settings are editable by the Organization Owner.
 - Setup flow. Users are able to build an Organization on top of an existing top-level group. New users are able to create an Organization from scratch and to start building top-level groups from there.
 - Visibility. Options will be `public` and `private`. A nonuser of a specific Organization will not see private Organizations in the explore section. Visibility is editable by the Organization Owner.
-- Organization settings page with the added ability to remove an Organization. Deletion of the default Organization is prevented. 
+- Organization settings page with the added ability to remove an Organization. Deletion of the default Organization is prevented.
 - Groups. This includes the ability to create, edit, and delete groups, as well as a Groups overview that can be accessed by the Organization Owner.
 - Projects. This includes the ability to create, edit, and delete projects, as well as a Projects overview that can be accessed by the Organization Owner.
 
@@ -146,9 +146,9 @@ In iteration 2, an Organization MVC Experiment will be released. We will test th
 
 ### Iteration 3: Organization MVC Beta (FY24Q4)
 
-In iteration 3, the Organization MVC Beta will be released. 
+In iteration 3, the Organization MVC Beta will be released.
 
-- Multiple Organization Owners can be assigned. 
+- Multiple Organization Owners can be assigned.
 - Enterprise users can be added to an Organization.
 
 ### Iteration 4: Organization MVC GA (FY25Q1)
@@ -160,7 +160,7 @@ After the initial rollout of Organizations, the following functionality will be
 1. Internal visibility will be made available on Organizations that are part of GitLab.com.
 1. Move billing from top-level group to Organization.
 1. Audit events at the Organization level.
-1. Set merge request approval rules at the Organization level and cascade to all groups and projects. 
+1. Set merge request approval rules at the Organization level and cascade to all groups and projects.
 1. Security policies at the Organization level.
 1. Vulnerability reports at the Organization level.
 1. Cascading Organization setting to enforce security scans.
diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md
index 43204b463b3..e36d57108ab 100644
--- a/doc/ci/runners/runners_scope.md
+++ b/doc/ci/runners/runners_scope.md
@@ -95,7 +95,7 @@ To disable shared runners for a group:
    select **Allow projects and subgroups to override the group setting**.
 
 NOTE:
-If you re-enable the shared runners for a group after you disable them, a user with the 
+If you re-enable the shared runners for a group after you disable them, a user with the
 Owner or Maintainer role must manually change this setting for each project subgroup or project.
 
 ### How shared runners pick jobs
diff --git a/doc/ci/runners/saas/linux_saas_runner.md b/doc/ci/runners/saas/linux_saas_runner.md
index f1ae1a368bc..055cf651067 100644
--- a/doc/ci/runners/saas/linux_saas_runner.md
+++ b/doc/ci/runners/saas/linux_saas_runner.md
@@ -89,7 +89,8 @@ Below are the settings for SaaS runners on Linux.
   [distributed cache](https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching)
   that's stored in a Google Cloud Storage (GCS) bucket. Cache contents not updated in
   the last 14 days are automatically removed, based on the
-  [object lifecycle management policy](https://cloud.google.com/storage/docs/lifecycle).
+  [object lifecycle management policy](https://cloud.google.com/storage/docs/lifecycle). The maximum size of an 
+  uploaded cache artifact can be 5GB after the cache becomes a compressed archive.
 
 - **Timeout settings**: Jobs handled by the SaaS Runners on Linux
   **time out after 3 hours**, regardless of the timeout configured in a
diff --git a/doc/development/ai_architecture.md b/doc/development/ai_architecture.md
index e9994c8a6f4..ac62f50baf5 100644
--- a/doc/development/ai_architecture.md
+++ b/doc/development/ai_architecture.md
@@ -84,7 +84,7 @@ Web --> AIF
 
 GitLab currently operates a cloud-hosted AI architecture. We are exploring how self-managed instances integrate with it.
 
-There are two primary reasons for this: the best AI models are cloud-based as they often depend on specialized hardware designed for this purpose, and operating self-managed infrastructure capable of AI at-scale and with appropriate performance is a significant undertaking. We are actively [tracking self-managed customers interested in AI](https://gitlab.com/gitlab-org/gitlab/-/issues/409183). 
+There are two primary reasons for this: the best AI models are cloud-based as they often depend on specialized hardware designed for this purpose, and operating self-managed infrastructure capable of AI at-scale and with appropriate performance is a significant undertaking. We are actively [tracking self-managed customers interested in AI](https://gitlab.com/gitlab-org/gitlab/-/issues/409183).
 
 ## Supported technologies
 
diff --git a/doc/gitlab-basics/start-using-git.md b/doc/gitlab-basics/start-using-git.md
index fd322b67abe..c824fc2e44f 100644
--- a/doc/gitlab-basics/start-using-git.md
+++ b/doc/gitlab-basics/start-using-git.md
@@ -276,7 +276,7 @@ git checkout -b <name-of-branch>
 ```
 
 GitLab enforces [branch naming rules](../user/project/repository/branches/index.md#name-your-branch)
-to prevent problems, and provides 
+to prevent problems, and provides
 [branch naming patterns](../user/project/repository/branches/index.md#prefix-branch-names-with-issue-numbers)
 to streamline merge request creation.
 
diff --git a/doc/raketasks/backup_gitlab.md b/doc/raketasks/backup_gitlab.md
index 890cbaf8b3b..6a17a808983 100644
--- a/doc/raketasks/backup_gitlab.md
+++ b/doc/raketasks/backup_gitlab.md
@@ -21,6 +21,7 @@ including:
 - Packages ([introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/332006) in GitLab 14.7)
 - Snippets
 - [Group wikis](../user/project/wiki/group.md)
+- Project-level Secure Files ([introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/121142) in GitLab 16.1)
 
 Backups do not include:
 
@@ -240,6 +241,7 @@ You can exclude specific directories from the backup by adding the environment v
 - `pages` (Pages content)
 - `repositories` (Git repositories data)
 - `packages` (Packages)
+- `ci_secure_files` (Project-level Secure Files)
 
 NOTE:
 When [backing up and restoring Helm Charts](https://docs.gitlab.com/charts/architecture/backup-restore.html), there is an additional option `packages`, which refers to any packages managed by the GitLab [package registry](../user/packages/package_registry/index.md).
diff --git a/doc/topics/gitlab_flow.md b/doc/topics/gitlab_flow.md
index eb298841247..f40d59ad7e4 100644
--- a/doc/topics/gitlab_flow.md
+++ b/doc/topics/gitlab_flow.md
@@ -311,7 +311,7 @@ In GitLab Flow, you can configure your pipeline to run every time you commit cha
 When you are ready to merge your feature branch, assign the merge request to a maintainer for the project.
 Also, mention any other people from whom you would like feedback.
 After the assigned person feels comfortable with the result, they can merge the branch.
-In GitLab Flow, a [merged results pipeline](../ci/pipelines/merged_results_pipelines.md) runs against the results of the source and target branches merged together. 
+In GitLab Flow, a [merged results pipeline](../ci/pipelines/merged_results_pipelines.md) runs against the results of the source and target branches merged together.
 If the assigned person does not feel comfortable, they can request more changes or close the merge request without merging.
 
 NOTE:
@@ -513,7 +513,7 @@ The words "change," "improve," "fix," and "refactor" don't add much information
 For more information, see Tim Pope's excellent [note about formatting commit messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 
 To add more context to a commit message, consider adding information regarding the
-origin of the change, such the GitLab issue URL or Jira issue number. That way, you provide 
+origin of the change, such the GitLab issue URL or Jira issue number. That way, you provide
 more information for users who need in-depth context about the change.
 
 For example:
diff --git a/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md b/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md
new file mode 100644
index 00000000000..bf8f25081c4
--- /dev/null
+++ b/doc/tutorials/configure_gitlab_runner_to_use_gke/index.md
@@ -0,0 +1,201 @@
+---
+stage: Verify
+group: Runner
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
+---
+
+# Tutorial: Configure GitLab Runner to use the Google Kubernetes Engine
+
+This tutorial describes how to configure GitLab Runner to use the Google Kubernetes Engine (GKE)
+to run jobs.
+
+In this tutorial, you configure GitLab Runner to run jobs in the following [GKE cluster modes](https://cloud.google.com/kubernetes-engine/docs/concepts/types-of-clusters):
+
+- Autopilot
+- Standard
+
+To configure GitLab Runner to use the GKE:
+
+1. [Set up your environment](#set-up-your-environment).
+1. [Create and connect to a cluster](#create-and-connect-to-a-cluster).
+1. [Install and configure the Kubernetes Operator](#install-and-configure-the-kubernetes-operator).
+1. Optional. [Verify that the configuration was successful](#verify-your-configuration).
+
+## Prerequisites
+
+Before you can configure GitLab Runner to use the GKE you must:
+
+- Have a project where you have the Maintainer or Owner role. If you don't have a project, you can [create it](../../user/project/index.md).
+- [Obtain the project runner registration token](../../ci/runners/register_runner.md#generate-a-registration-token-deprecated).
+- Install GitLab Runner.
+
+## Set up your environment
+
+Install the tools to configure and use GitLab Runner in the GKE.
+
+1. [Install and configure Google Cloud CLI](https://cloud.google.com/sdk/docs/install). You use Google Cloud CLI to connect to the cluster.
+1. [Install and configure kubectl](https://kubernetes.io/docs/tasks/tools/). You use kubectl to communicate with the remote cluster from your local environment.
+
+## Create and connect to a cluster
+
+This step describes how to create a cluster and connect to it. After you connect to the cluster, you use kubectl to interact with it
+and, for autopilot clusters, to add configurations that specify which jobs to run.
+
+1. In the Google Cloud Platform, create an [autopilot](https://cloud.google.com/kubernetes-engine/docs/how-to/creating-an-autopilot-cluster) or [standard](https://cloud.google.com/kubernetes-engine/docs/how-to/creating-a-zonal-cluster) cluster.
+
+1. Install the kubectl authentication plugin:
+
+   ```shell
+   gcloud components install gke-gcloud-auth-plugin
+   ```
+
+1. Connect to the cluster:
+
+   ```shell
+   gcloud container clusters get-credentials CLUSTER_NAME --zone=CLUSTER_LOCATION
+   ```
+
+1. View the cluster configuration:
+
+   ```shell
+   kubectl config view
+   ```
+
+1. Verify that you are connected to the cluster:
+
+   ```shell
+   kubectl config view current-context
+   ```
+
+## Install and configure the Kubernetes Operator
+
+Now that you have a cluster, you're ready to install and configure the Kubernetes Operator.
+
+1. Install the prerequisites:
+
+   ```shell
+     kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.7.1/cert-manager.yaml
+   ```
+
+1. Install the Operator Lifecycle Manager (OLM), a tool that manages the Kubernetes Operators that
+   run on the cluster:
+
+   <!-- markdownlint-disable -->
+
+   ```shell
+   curl --silent --location "https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.24.0/install.sh" \
+    | bash -s v0.24.0
+   ```
+
+   <!-- markdownlint-enable -->
+
+1. Install the Kubernetes Operator Catalog:
+
+   ```shell
+   kubectl create -f https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/crds.yaml
+   kubectl create -f https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml
+   ```
+
+1. Install the Kubernetes Operator:
+
+   ```shell
+   kubectl create -f https://operatorhub.io/install/gitlab-runner-operator.yaml
+   ```
+
+1. Create a secret that contains the `runner-registration-token` from your
+   GitLab project:
+
+   ```shell
+    cat > gitlab-runner-secret.yml << EOF
+    apiVersion: v1
+    kind: Secret
+    metadata:
+      name: gitlab-runner-secret
+    type: Opaque
+    stringData:
+   runner-registration-token: YOUR_RUNNER_REGISTRATION_TOKEN
+   EOF
+   ```
+
+1. Apply the secret:
+
+   ```shell
+   kubectl apply -f gitlab-runner-secret.yml
+   ```
+
+1. For autopilot clusters, you must create a YAML file with additional
+   configuration details. Autopilot clusters use this file to instruct the
+   GKE about what resources the Pod needs so it can run the jobs. You don't
+   need to create this file for standard clusters. Here is an example configuration:
+
+   ```shell
+   cat > config.yml << EOF
+   apiVersion: v1
+   kind: configMaps
+   metadata:
+     name: config.toml
+   config: |
+   [[runners]]
+     [runners.kubernetes]
+       image = "alpine"
+       cpu_limit = "1"
+       memory_limit = "128Mi"
+       service_cpu_limit = "1"
+       service_memory_limit = "128Mi"
+       helper_cpu_limit = "500m"
+       helper_memory_limit = "100Mi"
+   ```
+
+1. Apply the `config.yml`:
+
+   ```shell
+   kubectl apply -f config.yml
+   ```
+
+1. Create the custom resource definition file and include the following information:
+
+   ```shell
+   cat > gitlab-runner.yml << EOF
+      apiVersion: apps.gitlab.com/v1beta2
+         kind: Runner
+         metadata:
+         name: gitlab-runner
+      spec:
+         gitlabUrl: https://gitlab.example.com
+         buildImage: alpine
+         config: "config.toml"  # <---- Reference to the config.toml configMap
+         token: gitlab-runner-secret
+      EOF
+   ```
+
+1. Apply the custom resource definition file:
+
+   ```shell
+   kubectl apply -f gitlab-runner.yml
+   ```
+
+That's it! You've configured GitLab Runner to use the GKE.
+In the next step, you can check if your configuration is working.
+
+## Verify your configuration
+
+To check if runners are running in the GKE cluster, you can either:
+
+- Use the following command:
+
+  ```shell
+  kubectl get pods
+  ```
+
+  You should see the following output, which shows your runners
+  are running in the GKE cluster:
+
+  ```plaintext
+  NAME                             READY   STATUS    RESTARTS   AGE
+  gitlab-runner-bf9894bdb-wplxn    1/1     Running   0          5m
+  ```
+
+- Check the job log in GitLab:
+  1. On the top bar, select **Main menu > Projects** and find the project.
+  1. On the left sidebar, select **CI/CD > Jobs** and find the job.
+  1. To view the job log, select the job status.
diff --git a/doc/update/zero_downtime.md b/doc/update/zero_downtime.md
index 0eb7a520850..c815087b0b3 100644
--- a/doc/update/zero_downtime.md
+++ b/doc/update/zero_downtime.md
@@ -94,7 +94,7 @@ meet the other online upgrade requirements mentioned above.
 
 WARNING:
 You can only upgrade one minor release at a time. So from 15.6 to 15.7, not to 15.8.
-If you attempt more than one minor release, the upgrade may fail. 
+If you attempt more than one minor release, the upgrade may fail.
 
 ### Use a load balancer in front of web (Puma) nodes
 
diff --git a/doc/user/admin_area/settings/usage_statistics.md b/doc/user/admin_area/settings/usage_statistics.md
index ef34bfbc151..f901ce46bf0 100644
--- a/doc/user/admin_area/settings/usage_statistics.md
+++ b/doc/user/admin_area/settings/usage_statistics.md
@@ -212,6 +212,7 @@ If there are problems with the manual upload:
 1. Open a confidential issue in the [security fork of version app project](https://gitlab.com/gitlab-org/security/version.gitlab.com).
 1. Attach the JSON payload if possible.
 1. Tag `@gitlab-org/analytics-section/analytics-instrumentation` who will triage the issue.
+
 <!-- ## Troubleshooting
 
 Include any troubleshooting steps that you can foresee. If you know beforehand what issues
diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md
index 77fca862a5b..5e76db35d5a 100644
--- a/doc/user/group/compliance_frameworks.md
+++ b/doc/user/group/compliance_frameworks.md
@@ -400,7 +400,7 @@ This configuration doesn't overwrite the compliance pipeline and you get the fol
 
 ### Prefilled variables are not shown
 
-Because of a [known issue](https://gitlab.com/gitlab-org/gitlab/-/issues/382857), 
+Because of a [known issue](https://gitlab.com/gitlab-org/gitlab/-/issues/382857),
 compliance pipelines in GitLab 15.3 and later can prevent
 [prefilled variables](../../ci/pipelines/index.md#prefill-variables-in-manual-pipelines)
 from appearing when manually starting a pipeline.
diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md
index 3549818e611..508b5b27600 100644
--- a/doc/user/group/manage.md
+++ b/doc/user/group/manage.md
@@ -427,7 +427,7 @@ This setting enables users in the group to access [Code Suggestions](../project/
 This setting [cascades to all projects](../project/merge_requests/approvals/settings.md#settings-cascading)
 that belong to the group.
 
-However, each user can enable or disable Code Suggestions for themselves. 
+However, each user can enable or disable Code Suggestions for themselves.
 
 To enable Code Suggestions for a group:
 
diff --git a/doc/user/project/repository/code_suggestions.md b/doc/user/project/repository/code_suggestions.md
index f22bb615036..e567f157fa3 100644
--- a/doc/user/project/repository/code_suggestions.md
+++ b/doc/user/project/repository/code_suggestions.md
@@ -60,7 +60,7 @@ Usage of Code Suggestions is governed by the [GitLab Testing Agreement](https://
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/121079) in GitLab 16.1 as [Beta](/ee/policy/alpha-beta-support.md#beta).
 
-Each user can enable Code Suggestions for themselves: 
+Each user can enable Code Suggestions for themselves:
 
 1. On the top bar, in the upper-right corner, select your avatar.
 1. On the left sidebar, select **Preferences**.