Add latest changes from gitlab-org/gitlab@master

27 files changed, 41 insertions, 43 deletions

diff --git a/doc/user/admin_area/settings/rate_limit_on_pipelines_creation.md b/doc/user/admin_area/settings/rate_limit_on_pipelines_creation.md
index 2819a18d361..fce6179f5cf 100644
--- a/doc/user/admin_area/settings/rate_limit_on_pipelines_creation.md
+++ b/doc/user/admin_area/settings/rate_limit_on_pipelines_creation.md
@@ -31,3 +31,4 @@ To limit the number of pipeline requests:
 1. Expand **Pipelines Rate Limits**.
 1. Under **Max requests per minute**, enter a value greater than `0`.
 1. Select **Save changes**.
+1. Enable `ci_enforce_throttle_pipelines_creation` feature flag to enable the rate limit.
diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md
index 017a0c46570..6d0b87d29e2 100644
--- a/doc/user/analytics/index.md
+++ b/doc/user/analytics/index.md
@@ -81,7 +81,7 @@ Deployment frequency displays in several charts:
 Lead time for changes measures the time to deliver a feature once it has been developed,
 as described in [Measuring DevOps Performance](https://devops.com/measuring-devops-performance/).
 
-Lead time for changes displays in several charts: 
+Lead time for changes displays in several charts:
 
 - [Group-level value stream analytics](../group/value_stream_analytics/index.md)
 - [Project-level value stream analytics](value_stream_analytics.md)
@@ -89,7 +89,7 @@ Lead time for changes displays in several charts:
 
 ### Time to restore service
 
-Time to restore service measures how long it takes an organization to recover from a failure in production. 
+Time to restore service measures how long it takes an organization to recover from a failure in production.
 GitLab measures this as the average time required to close the incidents
 in the given time period. This assumes:
 
@@ -99,7 +99,7 @@ one production deployment, and any production deployment is related to no more t
 
 To retrieve metrics for time to restore service, use the [GraphQL](../../api/graphql/reference/index.md) or the [REST](../../api/dora/metrics.md) APIs.
 
-### Change failure rate 
+### Change failure rate
 
 Change failure rate measures the percentage of deployments that cause a failure in production. GitLab measures this as the number
 of incidents divided by the number of deployments to a
diff --git a/doc/user/analytics/value_stream_analytics.md b/doc/user/analytics/value_stream_analytics.md
index 039d33a1ad8..a428db75a28 100644
--- a/doc/user/analytics/value_stream_analytics.md
+++ b/doc/user/analytics/value_stream_analytics.md
@@ -119,7 +119,7 @@ The **Lead Time for Changes** metrics display below the **Filter results** text
 To view deployment metrics, you must have a
 [production environment configured](../../ci/environments/index.md#deployment-tier-of-environments).
 
-Value stream analytics shows the following deployment metrics for your project:  
+Value stream analytics shows the following deployment metrics for your project:
 
 - Deploys: The number of successful deployments in the date range.
 - Deployment Frequency: The average number of successful deployments per day in the date range.
diff --git a/doc/user/application_security/coverage_fuzzing/index.md b/doc/user/application_security/coverage_fuzzing/index.md
index a5eca411858..f4404ed688f 100644
--- a/doc/user/application_security/coverage_fuzzing/index.md
+++ b/doc/user/application_security/coverage_fuzzing/index.md
@@ -145,7 +145,7 @@ You can download the JSON report file from the CI/CD pipelines page. For more in
 ## Corpus registry
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5017) in GitLab 14.8.
-> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/347187) in GitLab 14.9. [Feature flags `corpus_management` and `corpus_management_ui`](https://gitlab.com/gitlab-org/gitlab/-/issues/328418) removed.  
+> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/347187) in GitLab 14.9. [Feature flags `corpus_management` and `corpus_management_ui`](https://gitlab.com/gitlab-org/gitlab/-/issues/328418) removed.
 
 The corpus registry is a library of corpuses. Corpuses in a project's registry are available to
 all jobs in that project. A project-wide registry is a more efficient way to manage corpuses than
diff --git a/doc/user/application_security/dast/browser_based.md b/doc/user/application_security/dast/browser_based.md
index 4cde1847419..ffcd496e2c3 100644
--- a/doc/user/application_security/dast/browser_based.md
+++ b/doc/user/application_security/dast/browser_based.md
@@ -111,7 +111,7 @@ a page fully loaded. Browser-based scans consider a page loaded when:
 1. The [DOMContentLoaded](https://developer.mozilla.org/en-US/docs/Web/API/Window/DOMContentLoaded_event) event has fired.
 1. There are no open or outstanding requests that are deemed important, such as JavaScript and CSS. Media files are usually deemed unimportant.
 1. Depending on whether the browser executed a navigation, was forcibly transitioned, or action:
-  
+
    - There are no new Document Object Model (DOM) modification events after the `DAST_BROWSER_NAVIGATION_STABILITY_TIMEOUT`, `DAST_BROWSER_STABILITY_TIMEOUT`, or `DAST_BROWSER_ACTION_STABILITY_TIMEOUT` durations.
 
 After these events have occurred, browser-based scans consider the page loaded and ready, and attempt the next action.
diff --git a/doc/user/application_security/dast/checks/359.1.md b/doc/user/application_security/dast/checks/359.1.md
index af1fdf8a596..076ab2da0d5 100644
--- a/doc/user/application_security/dast/checks/359.1.md
+++ b/doc/user/application_security/dast/checks/359.1.md
@@ -8,8 +8,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 ## Description
 
-The target application was found to return credit card information in the response. Organizations 
-found returning such information may be in violation of industry regulations and could face fines. 
+The target application was found to return credit card information in the response. Organizations
+found returning such information may be in violation of industry regulations and could face fines.
 
 ## Remediation
 
@@ -17,7 +17,7 @@ PII such as credit cards should never be directly returned to the user. The majo
 the last few digits or characters of the identifier. For example, credit card numbers should
 only return the last four digits: `****-****-****-1234`. Ensure this masking is done on the server
 and only then send the masked data back to the client. Do not rely on client side JavaScript or other methods
-to mask these values as the data could still be intercepted or unmasked. 
+to mask these values as the data could still be intercepted or unmasked.
 
 Additionally, credit card information should never be stored un-encrypted in files or databases.
 
diff --git a/doc/user/application_security/dast/checks/359.2.md b/doc/user/application_security/dast/checks/359.2.md
index beb99e26097..2c59b5e321f 100644
--- a/doc/user/application_security/dast/checks/359.2.md
+++ b/doc/user/application_security/dast/checks/359.2.md
@@ -8,16 +8,16 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 ## Description
 
-The target application was found to return social security number (SSN) information in the response. Organizations 
-found returning such information may be in violation of (United States) state or federal laws and may face stiff penalties. 
+The target application was found to return social security number (SSN) information in the response. Organizations
+found returning such information may be in violation of (United States) state or federal laws and may face stiff penalties.
 
 ## Remediation
 
-PII such as social security numbers should never be directly returned to the user. The majority of the information 
+PII such as social security numbers should never be directly returned to the user. The majority of the information
 should masked except the last few digits or characters of the identifier. For example, social security numbers
 only be displayed with the last four digits: `***-**-1234`. Ensure this masking is done on the server
 and only then send the masked data back to the client. Do not rely on client side JavaScript or other methods
-to mask these values as the data could still be intercepted or unmasked. 
+to mask these values as the data could still be intercepted or unmasked.
 
 Additionally, social security numbers should never be stored un-encrypted in files or databases.
 
diff --git a/doc/user/application_security/index.md b/doc/user/application_security/index.md
index d22949c7285..d4b5c029b26 100644
--- a/doc/user/application_security/index.md
+++ b/doc/user/application_security/index.md
@@ -213,9 +213,9 @@ security issues:
 
 ### Migration of existing Vulnerability-Check rules
 
-If your projects have rules that have a security orchestration project, a new MR with 
+If your projects have rules that have a security orchestration project, a new MR with
 the existing rule's content is created automatically against the default branch belonging
-to the security orchestration project. To maintain the same security approval rules you 
+to the security orchestration project. To maintain the same security approval rules you
 had before GitLab 15.0, we recommend merging this new MR.
 
 If your projects have rules without a security orchestration project, a new security orchestration project is created automatically with the content of the existing rule. No additional action is required.
@@ -666,6 +666,3 @@ These security pages can be populated by running the jobs from the manual step o
 There is [an issue open to handle this scenario](https://gitlab.com/gitlab-org/gitlab/-/issues/346843).
 Please upvote the issue to help with prioritization, and
 [contributions are welcomed](https://about.gitlab.com/community/contribute/).
-  doc/user/project/merge_requests/approvals/settings.md 
-+
-0
diff --git a/doc/user/clusters/agent/gitops.md b/doc/user/clusters/agent/gitops.md
index 6ca9d855b44..3bd48390364 100644
--- a/doc/user/clusters/agent/gitops.md
+++ b/doc/user/clusters/agent/gitops.md
@@ -65,7 +65,7 @@ gitops:
   - id: gitlab-org/cluster-integration/gitlab-agent
     default_namespace: my-ns
     paths:
-      # Read all YAML files from this directory. 
+      # Read all YAML files from this directory.
     - glob: '/team1/app1/*.yaml'
       # Read all .yaml files from team2/apps and all subdirectories.
     - glob: '/team2/apps/**/*.yaml'
diff --git a/doc/user/group/index.md b/doc/user/group/index.md
index e3487ad73e0..f7271d6b9ee 100644
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -623,7 +623,7 @@ You should consider these security implications before configuring IP address re
     names and hierarchies. Only the [group](../../api/groups.md) (including all [group resources](../../api/api_resources.md#group-resources))
     APIs and [project](../../api/api_resources.md#project-resources) (including all [project resources](../../api/api_resources.md#project-resources))
     APIs are protected by IP address restrictions.
-- **Activities performed by GitLab Runners are not bound by IP restrictions**: 
+- **Activities performed by GitLab Runners are not bound by IP restrictions**:
   When you register a runner, it is not bound by the IP restrictions. When the runner
   requests a new job or an update to a job's state, it is also not bound by
   the IP restrictions. But when the running CI/CD job sends Git requests from a
diff --git a/doc/user/infrastructure/clusters/connect/new_gke_cluster.md b/doc/user/infrastructure/clusters/connect/new_gke_cluster.md
index be58b4565a1..7666ee4821e 100644
--- a/doc/user/infrastructure/clusters/connect/new_gke_cluster.md
+++ b/doc/user/infrastructure/clusters/connect/new_gke_cluster.md
@@ -98,7 +98,7 @@ Use CI/CD environment variables to configure your project.
 1. Set the variable `BASE64_GOOGLE_CREDENTIALS` to the `base64` encoded JSON file you just created.
 1. Set the variable `TF_VAR_gcp_project` to your GCP's `project` name.
 1. Set the variable `TF_VAR_agent_token` to the agent token displayed in the previous task.
-1. Set the variable `TF_VAR_kas_address` to the agent server address displayed in the previous task. 
+1. Set the variable `TF_VAR_kas_address` to the agent server address displayed in the previous task.
 
 **Optional configuration:**
 
diff --git a/doc/user/infrastructure/iac/terraform_state.md b/doc/user/infrastructure/iac/terraform_state.md
index f56fe92ec01..eeb65a46f0f 100644
--- a/doc/user/infrastructure/iac/terraform_state.md
+++ b/doc/user/infrastructure/iac/terraform_state.md
@@ -56,7 +56,7 @@ To configure GitLab CI/CD as a backend:
 1. In the root directory of your project repository, create a `.gitlab-ci.yml` file. Use
    [this file](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml)
    to populate it.
-   
+
 1. Push your project to GitLab. This action triggers a pipeline, which
    runs the `gitlab-terraform init`, `gitlab-terraform validate`, and
    `gitlab-terraform plan` commands.
diff --git a/doc/user/packages/container_registry/reduce_container_registry_data_transfer.md b/doc/user/packages/container_registry/reduce_container_registry_data_transfer.md
index 9dcb4d7127d..8f90f42ad08 100644
--- a/doc/user/packages/container_registry/reduce_container_registry_data_transfer.md
+++ b/doc/user/packages/container_registry/reduce_container_registry_data_transfer.md
@@ -114,8 +114,8 @@ up your builds and reduce the amount of data transferred. For more information,
 
 ## Check automation frequency
 
-We often create automation scripts bundled into container images to perform regular tasks on specific intervals. 
-You can reduce the frequency of those intervals in cases where the automation is pulling container images from 
+We often create automation scripts bundled into container images to perform regular tasks on specific intervals.
+You can reduce the frequency of those intervals in cases where the automation is pulling container images from
 the GitLab Registry to a service outside of GitLab.com.
 
 ## Move to GitLab Premium or Ultimate
diff --git a/doc/user/packages/go_proxy/index.md b/doc/user/packages/go_proxy/index.md
index d2edfcb94c5..733fd383a04 100644
--- a/doc/user/packages/go_proxy/index.md
+++ b/doc/user/packages/go_proxy/index.md
@@ -108,7 +108,7 @@ and add the following text. Replace the variables in `< >` with your values.
 
 WARNING:
 If you use an environment variable called `NETRC`, Go will use its value
-as a filename and ignore `~/.netrc`. If you intend to use `~/.netrc` in 
+as a filename and ignore `~/.netrc`. If you intend to use `~/.netrc` in
 the GitLab CI **do not use `NETRC` as an environment variable name**.
 
 ```plaintext
diff --git a/doc/user/packages/helm_repository/index.md b/doc/user/packages/helm_repository/index.md
index 73298afc9cd..88ea5afad3c 100644
--- a/doc/user/packages/helm_repository/index.md
+++ b/doc/user/packages/helm_repository/index.md
@@ -78,10 +78,10 @@ For example:
 
 ```yaml
 image: curlimages/curl:latest
- 
+
 stages:
   - upload
- 
+
 upload:
   stage: upload
   script:
diff --git a/doc/user/packages/npm_registry/index.md b/doc/user/packages/npm_registry/index.md
index 1f37e5639c6..bdcbea68568 100644
--- a/doc/user/packages/npm_registry/index.md
+++ b/doc/user/packages/npm_registry/index.md
@@ -397,7 +397,7 @@ If multiple packages have the same name and version, when you install a package,
 
    - Replace `@foo` with your scope.
    - Replace `gitlab.example.com` with your domain name.
-  
+
    For [project-level endpoints](#use-the-gitlab-endpoint-for-npm-packages) run:
 
    ```shell
diff --git a/doc/user/permissions.md b/doc/user/permissions.md
index 433274c63b9..a141806c813 100644
--- a/doc/user/permissions.md
+++ b/doc/user/permissions.md
@@ -232,7 +232,7 @@ The following table lists project permissions available for each role:
 15. Guest users can only set metadata (for example, labels, assignees, or milestones)
     when creating an issue. They cannot change the metadata on existing issues.
 16. In GitLab 14.5 or later, Guests are not allowed to [create incidents](../operations/incident_management/incidents.md#incident-creation).
-    A guest who created an incident when they had the Reporter role or who is assigned to the incident can modify the title, description and metrics. They can also close and reopen the incident.
+    In GitLab 15.1 and later, a Guest who created an issue that was promoted to an incident cannot edit, close, or reopen their incident.
 17. In projects that accept contributions from external members, users can create, edit, and close their own merge requests.
 18. Authors and assignees of issues can modify the title and description even if they don't have the Reporter role.
 19. Authors and assignees can close and reopen issues even if they don't have the Reporter role.
diff --git a/doc/user/profile/index.md b/doc/user/profile/index.md
index 931fd0be23b..1ec89750c0b 100644
--- a/doc/user/profile/index.md
+++ b/doc/user/profile/index.md
@@ -399,7 +399,7 @@ You can add this URL to your feed reader.
 
 ### Reset the user activity feed token
 
-Feed tokens are sensitive and can reveal information from confidential issues. 
+Feed tokens are sensitive and can reveal information from confidential issues.
 If you think your feed token has been exposed, you should reset it.
 
 To reset your feed token:
@@ -408,7 +408,7 @@ To reset your feed token:
 1. Select **Edit profile**.
 1. On the left sidebar, select **Access Tokens**.
 1. Scroll down. In the **Feed token** section, select the
-   **reset this token** link. 
+   **reset this token** link.
 1. On the confirmation box, select **OK**.
 
 A new token is generated.
diff --git a/doc/user/project/code_owners.md b/doc/user/project/code_owners.md
index e37ff560080..197a995952a 100644
--- a/doc/user/project/code_owners.md
+++ b/doc/user/project/code_owners.md
@@ -255,7 +255,7 @@ README @group @group/with-nested/subgroup
 /docs/* @root-docs
 
 # Include `/**` to specify Code Owners for all subdirectories
-# in a directory. This rule matches `docs/projects/index.md` or 
+# in a directory. This rule matches `docs/projects/index.md` or
 # `docs/development/index.md`
 /docs/**/*.md @root-docs
 
diff --git a/doc/user/project/integrations/harbor.md b/doc/user/project/integrations/harbor.md
index 2a1b12057aa..a952abf691d 100644
--- a/doc/user/project/integrations/harbor.md
+++ b/doc/user/project/integrations/harbor.md
@@ -31,7 +31,7 @@ GitLab supports integrating Harbor projects at the group or project level. Compl
 1. Turn on the **Active** toggle under **Enable Integration**.
 1. Provide the Harbor configuration information:
    - **Harbor URL**: The base URL of Harbor instance which is being linked to this GitLab project. For example, `https://harbor.example.net`.
-   - **Harbor project name**: The project name in the Harbor instance. For example, `testproject`.  
+   - **Harbor project name**: The project name in the Harbor instance. For example, `testproject`.
    - **Username**: Your username in the Harbor instance, which should meet the requirements in [prerequisites](#prerequisites).
    - **Password**: Password of your username.
 
diff --git a/doc/user/project/integrations/zentao.md b/doc/user/project/integrations/zentao.md
index 67125c3ebbf..32e07c0b6e9 100644
--- a/doc/user/project/integrations/zentao.md
+++ b/doc/user/project/integrations/zentao.md
@@ -12,9 +12,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 ## Configure ZenTao
 
-This integration requires a ZenTao API secret key.  
+This integration requires a ZenTao API secret key.
 
-Complete these steps in ZenTao:  
+Complete these steps in ZenTao:
 
 1. Go to your **Admin** page and select **Develop > Application**.
 1. Select **Add Application**.
@@ -32,7 +32,7 @@ Complete these steps in GitLab:
 1. Turn on the **Active** toggle under **Enable Integration**.
 1. Provide the ZenTao configuration information:
    - **ZenTao Web URL**: The base URL of the ZenTao instance web interface you're linking to this GitLab project (for example, `example.zentao.net`).
-   - **ZenTao API URL** (optional): The base URL to the ZenTao instance API. Defaults to the Web URL value if not set.  
+   - **ZenTao API URL** (optional): The base URL to the ZenTao instance API. Defaults to the Web URL value if not set.
    - **ZenTao API token**: Use the key you generated when you [configured ZenTao](#configure-zentao).
    - **ZenTao Product ID**: To display issues from a single ZenTao product in a given GitLab project. The Product ID can be found in the ZenTao product page under **Settings > Overview**.
 
diff --git a/doc/user/project/issues/csv_import.md b/doc/user/project/issues/csv_import.md
index a3f6ee5e61e..2fe3d78194c 100644
--- a/doc/user/project/issues/csv_import.md
+++ b/doc/user/project/issues/csv_import.md
@@ -25,7 +25,7 @@ To import issues:
 
 1. Go to your project's Issues list page.
 1. Open the import feature, depending if the project has issues:
-   - Existing issues are present: Select the import icon at the top right, next to **Edit issues**. 
+   - Existing issues are present: Select the import icon at the top right, next to **Edit issues**.
    - Project has no issues: Select **Import CSV** in the middle of the page.
 1. Select the file you want to import, and then select **Import issues**.
 
diff --git a/doc/user/project/merge_requests/accessibility_testing.md b/doc/user/project/merge_requests/accessibility_testing.md
index 612f499bb65..b8907532066 100644
--- a/doc/user/project/merge_requests/accessibility_testing.md
+++ b/doc/user/project/merge_requests/accessibility_testing.md
@@ -46,10 +46,10 @@ To define the `a11y` job for GitLab 12.9 and later:
    ```yaml
    stages:
      - accessibility
-   
+
    variables:
      a11y_urls: "https://about.gitlab.com https://gitlab.com/users/sign_in"
-   
+
    include:
      - template: "Verify/Accessibility.gitlab-ci.yml"
    ```
diff --git a/doc/user/project/merge_requests/approvals/index.md b/doc/user/project/merge_requests/approvals/index.md
index f0ab4d606ad..a91c4c0725c 100644
--- a/doc/user/project/merge_requests/approvals/index.md
+++ b/doc/user/project/merge_requests/approvals/index.md
@@ -103,7 +103,7 @@ Without the approvals, the work cannot merge. Required approvals enable multiple
   to determine who should review the work.
 - Require an [approval before merging code that causes test coverage to decline](../../../../ci/pipelines/settings.md#coverage-check-approval-rule)
 - Users on GitLab Ultimate can also [require approval from a security team](../../../application_security/index.md#security-approvals-in-merge-requests)
-  before merging code that could introduce a vulnerability. 
+  before merging code that could introduce a vulnerability.
 
 ## Related topics
 
diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md
index bfc83aa22f5..87e3c7f3311 100644
--- a/doc/user/project/working_with_projects.md
+++ b/doc/user/project/working_with_projects.md
@@ -73,7 +73,7 @@ To create a project in GitLab:
    - Create a [blank project](#create-a-blank-project).
    - Create a project from a:
       - [built-in template](#create-a-project-from-a-built-in-template).
-      - [custom template](#create-a-project-from-a-custom-template).  
+      - [custom template](#create-a-project-from-a-custom-template).
       - [HIPAA audit protocol template](#create-a-project-from-the-hipaa-audit-protocol-template).
    - [Import a project](../../user/project/import/index.md)
      from a different repository. Contact your GitLab administrator if this option is not available.
diff --git a/doc/user/search/global_search/advanced_search_syntax.md b/doc/user/search/global_search/advanced_search_syntax.md
index 3aa016f0bff..5604177431c 100644
--- a/doc/user/search/global_search/advanced_search_syntax.md
+++ b/doc/user/search/global_search/advanced_search_syntax.md
@@ -18,7 +18,7 @@ Advanced Search searches default project branches only.
 
 ## General search
 
-<!-- markdownlint-disable --> 
+<!-- markdownlint-disable -->
 
 | Use | Description  | Example                                                                                                                                        |
 |-----|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
diff --git a/doc/user/usage_quotas.md b/doc/user/usage_quotas.md
index 21aa93d3f8b..fd658c96184 100644
--- a/doc/user/usage_quotas.md
+++ b/doc/user/usage_quotas.md
@@ -50,7 +50,7 @@ The following storage usage statistics are available to a maintainer:
 
 ## Manage your storage usage
 
-You can use several methods to manage and reduce your usage for some storage types. 
+You can use several methods to manage and reduce your usage for some storage types.
 
 For more information, see the following pages: