Add latest changes from gitlab-org/gitlab@master

9 files changed, 70 insertions, 29 deletions

diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index b6a8cbae0da..539f1c1d33f 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -1341,6 +1341,28 @@ Input type: `BulkRunnerDeleteInput`
 | <a id="mutationbulkrunnerdeletedeletedids"></a>`deletedIds` | [`[CiRunnerID!]`](#cirunnerid) | IDs of records effectively deleted. Only present if operation was performed synchronously. |
 | <a id="mutationbulkrunnerdeleteerrors"></a>`errors` | [`[String!]!`](#string) | Errors encountered during execution of the mutation. |
 
+### `Mutation.catalogResourcesCreate`
+
+WARNING:
+**Introduced** in 15.11.
+This feature is in Alpha. It can be changed or removed at any time.
+
+Input type: `CatalogResourcesCreateInput`
+
+#### Arguments
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="mutationcatalogresourcescreateclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
+| <a id="mutationcatalogresourcescreateprojectpath"></a>`projectPath` | [`ID!`](#id) | Project to convert to a catalog resource. |
+
+#### Fields
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="mutationcatalogresourcescreateclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
+| <a id="mutationcatalogresourcescreateerrors"></a>`errors` | [`[String!]!`](#string) | Errors encountered during execution of the mutation. |
+
 ### `Mutation.ciCdSettingsUpdate`
 
 WARNING:
@@ -18335,6 +18357,7 @@ Represents a product analytics dashboard visualization.
 | <a id="projectid"></a>`id` | [`ID!`](#id) | ID of the project. |
 | <a id="projectimportstatus"></a>`importStatus` | [`String`](#string) | Status of import background job of the project. |
 | <a id="projectincidentmanagementtimelineeventtags"></a>`incidentManagementTimelineEventTags` | [`[TimelineEventTagType!]`](#timelineeventtagtype) | Timeline event tags for the project. |
+| <a id="projectiscatalogresource"></a>`isCatalogResource` **{warning-solid}** | [`Boolean`](#boolean) | **Introduced** in 15.11. This feature is in Alpha. It can be changed or removed at any time. Indicates if a project is a catalog resource. |
 | <a id="projectissuesenabled"></a>`issuesEnabled` | [`Boolean`](#boolean) | Indicates if Issues are enabled for the current user. |
 | <a id="projectjiraimportstatus"></a>`jiraImportStatus` | [`String`](#string) | Status of Jira import background job of the project. |
 | <a id="projectjiraimports"></a>`jiraImports` | [`JiraImportConnection`](#jiraimportconnection) | Jira imports into the project. (see [Connections](#connections)) |
diff --git a/doc/ci/migration/circleci.md b/doc/ci/migration/circleci.md
index d39ae88a4a9..64f6866a3a4 100644
--- a/doc/ci/migration/circleci.md
+++ b/doc/ci/migration/circleci.md
@@ -320,16 +320,14 @@ Example of the same job using `tags` in GitLab CI/CD:
 
 ```yaml
 windows job:
-  stage:
-    - build
+  stage: build
   tags:
     - windows
   script:
     - echo Hello, %USERNAME%!
 
 osx job:
-  stage:
-    - build
+  stage: build
   tags:
     - osx
   script:
diff --git a/doc/ci/runners/configure_runners.md b/doc/ci/runners/configure_runners.md
index cc30f661bf2..e3a6bed9b53 100644
--- a/doc/ci/runners/configure_runners.md
+++ b/doc/ci/runners/configure_runners.md
@@ -280,16 +280,14 @@ example, if you have an OS X runner with tag `osx` and a Windows runner with tag
 
 ```yaml
 windows job:
-  stage:
-    - build
+  stage: build
   tags:
     - windows
   script:
     - echo Hello, %USERNAME%!
 
 osx job:
-  stage:
-    - build
+  stage: build
   tags:
     - osx
   script:
diff --git a/doc/ci/yaml/includes.md b/doc/ci/yaml/includes.md
index 6d34a3034f7..252cef0aa97 100644
--- a/doc/ci/yaml/includes.md
+++ b/doc/ci/yaml/includes.md
@@ -405,7 +405,8 @@ see this [CI/CD variable demo](https://youtu.be/4XR8gw3Pkos).
 > - Introduced in GitLab 14.2 [with a flag](../../administration/feature_flags.md) named `ci_include_rules`. Disabled by default.
 > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/337507) in GitLab 14.3.
 > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/337507) in GitLab 14.4. Feature flag `ci_include_rules` removed.
-> - [Support for `exists` keyword added](https://gitlab.com/gitlab-org/gitlab/-/issues/341511) in GitLab 14.5.
+> - Support for `exists` keyword [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/341511) in GitLab 14.5.
+> - Support for `needs` job dependency [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/345377) in GitLab 15.11.
 
 You can use [`rules`](index.md#rules) with `include` to conditionally include other configuration files.
 
@@ -415,11 +416,6 @@ these keywords:
 - [`rules:if`](index.md#rulesif).
 - [`rules:exists`](index.md#rulesexists).
 
-You cannot use [`needs:`](index.md#needs) to create a job dependency that points to
-a job added with `include:local:rules`. When the configuration is validated,
-GitLab returns `undefined need: <job-name>`. [Issue 345377](https://gitlab.com/gitlab-org/gitlab/-/issues/345377)
-proposes improving this behavior.
-
 ### `include` with `rules:if`
 
 Use [`rules:if`](index.md#rulesif) to conditionally include other configuration files
diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md
index 01173f43c2e..ca422b2eabd 100644
--- a/doc/ci/yaml/index.md
+++ b/doc/ci/yaml/index.md
@@ -2556,11 +2556,10 @@ can use that variable in `needs:pipeline` to download artifacts from the parent
 To need a job that sometimes does not exist in the pipeline, add `optional: true`
 to the `needs` configuration. If not defined, `optional: false` is the default.
 
-Jobs that use [`rules`](#rules), [`only`, or `except`](#only--except) might not always
-be added to a pipeline. GitLab checks the `needs` relationships before starting a
-pipeline:
+Jobs that use [`rules`](#rules), [`only`, or `except`](#only--except) and that are added with [`include`](#include)
+might not always be added to a pipeline. GitLab checks the `needs` relationships before starting a pipeline:
 
-- If the needs entry has `optional: true` and the needed job is present in the pipeline,
+- If the `needs` entry has `optional: true` and the needed job is present in the pipeline,
   the job waits for it to complete before starting.
 - If the needed job is not present, the job can start when all other needs requirements are met.
 - If the `needs` section contains only optional jobs, and none are added to the pipeline,
@@ -3963,9 +3962,9 @@ If `stage` is not defined, the job uses the `test` stage by default.
 
 **Keyword type**: Job keyword. You can use it only as part of a job.
 
-**Possible inputs**: An array including any number of stage names. Stage names can be:
+**Possible inputs**: A string, which can be a:
 
-- The [default stages](#stages).
+- [Default stage](#stages).
 - User-defined stages.
 
 **Example of `stage`**:
diff --git a/doc/development/code_owners/index.md b/doc/development/code_owners/index.md
index fa0385777e8..e4a9cf0c290 100644
--- a/doc/development/code_owners/index.md
+++ b/doc/development/code_owners/index.md
@@ -28,6 +28,15 @@ namespace. Code Owners is an EE-only feature, so the files only exist in the `./
 
 - `Gitlab::CodeOwners`: the main module used to interact with the code owner rules.
   - Defined in `./ee/lib/gitlab/code_owners.rb`.
+- `Gitlab::CodeOwners::File`: wraps a `CODEOWNERS` file and exposes the data through
+  the class' public methods.
+  - Defined in `./ee/lib/gitlab/code_owners/file.rb`.
+- `Gitlab::CodeOwners::Section`: wraps a section heading from a
+  `CODEOWNERS` file and parses the different parts.
+  - Defined in `./ee/lib/gitlab/code_owners/section.rb`.
+- `Gitlab::CodeOwners::Entry`: wraps an entry (a pattern and owners line) in a
+  `CODEOWNERS` file and exposes the data through the class' public methods.
+  - Defined in `./ee/lib/gitlab/code_owners/entry.rb`.
 - `Gitlab::CodeOwners::Loader`: finds the correct `CODEOWNER` file and loads the
   content into a `Gitlab::CodeOwners::File` instance.
   - Defined in `./ee/lib/gitlab/code_owners/loader.rb`.
@@ -40,12 +49,6 @@ namespace. Code Owners is an EE-only feature, so the files only exist in the `./
 - `Gitlab::CodeOwners::GroupsLoader`: finds the correct `CODEOWNER` file and loads
   the content into a `Gitlab::CodeOwners::File` instance.
   - Defined in `./ee/lib/gitlab/code_owners/groups_loader.rb`.
-- `Gitlab::CodeOwners::File`: wraps a `CODEOWNERS` file and exposes the data through
-  the class' public methods.
-  - Defined in `./ee/lib/gitlab/code_owners/file.rb`.
-- `Gitlab::CodeOwners::Entry`: wraps an entry (a pattern and owners line) in a
-  `CODEOWNERS` file and exposes the data through the class' public methods.
-  - Defined in `./ee/lib/gitlab/code_owners/entry.rb`.
 - `Gitlab::CodeOwners::Validator`: validates no files in the `CODEOWNERS` entries
   have been changed when a user pushes to a protected branch with `require_code_owner_approval` enabled.
   - Defined in `./ee/lib/gitlab/code_owners/validator.rb`.
diff --git a/doc/development/internal_api/index.md b/doc/development/internal_api/index.md
index ea4846f966a..1c7499f1b6d 100644
--- a/doc/development/internal_api/index.md
+++ b/doc/development/internal_api/index.md
@@ -811,8 +811,8 @@ Example response:
 
 ## Storage limit exclusions
 
-The namespace storage limit exclusions endpoint applies storage limit exclusions to top-level namespaces on GitLab.com.
-This endpoint can only be consumed in the Admin Area of GitLab.com.
+The namespace storage limit exclusions endpoints manage storage limit exclusions on top-level namespaces on GitLab.com.
+These endpoints can only be consumed in the Admin Area of GitLab.com.
 
 ### Create a storage limit exclusion
 
@@ -849,6 +849,28 @@ Example response:
 }
 ```
 
+### Delete a storage limit exclusion
+
+Use a DELETE request to delete a `Namespaces::Storage::LimitExclusion` for a namespace.
+
+```plaintext
+DELETE /namespaces/:id/storage/limit_exclusion
+```
+
+Example request:
+
+```shell
+curl --request DELETE \
+  --url "https://gitlab.com/v4/namespaces/123/storage/limit_exclusion" \
+  --header 'PRIVATE-TOKEN: <admin access token>'
+```
+
+Example response:
+
+```plaintext
+204
+```
+
 ### Known consumers
 
 - GitLab.com Admin Area
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md
index ce5eae9d48d..d684d4d018f 100644
--- a/doc/update/deprecations.md
+++ b/doc/update/deprecations.md
@@ -244,7 +244,7 @@ In GitLab 14.4 we introduced the ability to limit the "outbound" scope of the CI
 
 In 15.9 we extended this functionality with a better solution, an "inbound" scope limit. You can prevent the job tokens from _other_ projects from being used to access your project. With this feature, you can optionally list specific projects that you want to allow to access your project with _their_ job token.
 
-In 16.0, this inbound scope limit will be the only option available for all projects, and the outbound limit setting will be removed. To prepare for this change, you can enable the ["inbound" CI/CD job token limit](https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html#configure-the-job-token-scope-limit) feature now, and list any projects that need to access your project.
+In 16.0, this inbound scope limit will be the only option available for all projects, and the outbound limit setting will be disabled. To prepare for this change, you can enable the ["inbound" CI/CD job token limit](https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html#configure-the-job-token-scope-limit) feature now, and list any projects that need to access your project.
 
 </div>
 
diff --git a/doc/user/search/exact_code_search.md b/doc/user/search/exact_code_search.md
index df7d029b821..674b2813985 100644
--- a/doc/user/search/exact_code_search.md
+++ b/doc/user/search/exact_code_search.md
@@ -26,5 +26,7 @@ expressions, certain special characters will require escaping. Backslash can
 escape special characters and wrapping in double quotes can be used for phrase
 searches.
 
+## Syntax
+
 To understand the possible filtering options, see the
 [Zoekt query syntax](https://github.com/sourcegraph/zoekt/blob/main/doc/query_syntax.md).