Add latest changes from gitlab-org/gitlab@master

4 files changed, 102 insertions, 61 deletions

diff --git a/doc/user/application_security/policies/scan-result-policies.md b/doc/user/application_security/policies/scan-result-policies.md
index 33db2695732..5b2a7062cb9 100644
--- a/doc/user/application_security/policies/scan-result-policies.md
+++ b/doc/user/application_security/policies/scan-result-policies.md
@@ -300,13 +300,20 @@ actions:
 
 ## Understanding scan result policy approvals
 
+> The branch comparison logic for `scan_finding` was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/428518) in GitLab 16.8 [with a flag](../../../administration/feature_flags.md) named `scan_result_policy_merge_base_pipeline`. Disabled by default.
+
+FLAG:
+On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `scan_result_policy_merge_base_pipeline`.
+On GitLab.com, this feature is not available.
+
 ### Scope of scan result policy comparison
 
 - To determine when approval is required on a merge request, we compare completed pipelines for each supported pipeline source for the source and target branch (for example, `feature`/`main`). This ensures the most comprehensive evaluation of scan results.
 - For the source branch, the comparison pipeline is its latest completed `HEAD` pipeline.
-- For the target branch, the comparison pipeline differs for `license_finding` rules:
-  - For `license_finding` rules, we compare to a common ancestor's latest completed pipeline.
-  - For all other rules, we compare to the target branch's latest completed `HEAD` pipeline.
+- For `license_finding` rules, we compare to a common ancestor's latest completed pipeline.
+- For `scan_finding` rules, the comparison pipeline may differ:
+  - If the `scan_result_policy_merge_base_pipeline` feature flag is enabled, we compare to a common ancestor's latest completed pipeline.
+  - Otherwise, we compare to the target branch's latest completed `HEAD` pipeline.
 - Scan result policies considers all supported pipeline sources (based on the [`CI_PIPELINE_SOURCE` variable](../../../ci/variables/predefined_variables.md)) when comparing results from both the source and target branches when determining if a merge request requires approval. Pipeline sources `webide` and `parent_pipeline` are not supported.
 
 ### Accepting risk and ignoring vulnerabilities in future merge requests
diff --git a/doc/user/markdown.md b/doc/user/markdown.md
index 0ec60a9274a..aafae095fc3 100644
--- a/doc/user/markdown.md
+++ b/doc/user/markdown.md
@@ -109,6 +109,8 @@ The following features are not found in standard Markdown.
 
 ### Colors
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#colors).
+
 Markdown does not support changing text color.
 
 You can write a color code in the formats: `HEX`, `RGB`, or `HSL`.
@@ -134,9 +136,6 @@ display a color chip next to the color code. For example:
 - `HSLA(540,70%,50%,0.3)`
 ```
 
-[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#colors)
-to see the color chips next to the color code:
-
 - `#F00`
 - `#F00A`
 - `#FF0000`
@@ -159,6 +158,8 @@ In wikis, you can also add and edit diagrams created with the [diagrams.net edit
 
 #### Mermaid
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#mermaid).
+
 Visit the [official page](https://mermaidjs.github.io/) for more details. The
 [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor/) helps you
 learn Mermaid and debug issues in your Mermaid code. Use it to identify and resolve
@@ -480,11 +481,6 @@ To include task lists in tables, [use HTML list tags or HTML tables](#task-lists
 
 ### Table of contents
 
-<!--
-Tags for the table of contents are presented in a code block to work around a Markdown bug.
-Do not change the code block back to single backticks.
-For more information, see https://gitlab.com/gitlab-org/gitlab/-/issues/359077.
--->
 A table of contents is an unordered list that links to subheadings in the document.
 You can add a table of contents to issues, merge requests, and epics, but you can't add one
 to notes or comments.
@@ -492,9 +488,15 @@ to notes or comments.
 Add one of these tags on their own line to the **description** field of any of the supported
 content types:
 
+<!--
+Tags for the table of contents are presented in a code block to work around a Markdown bug.
+Do not change the code block back to single backticks.
+For more information, see https://gitlab.com/gitlab-org/gitlab/-/issues/359077.
+-->
+
 ```markdown
 [[_TOC_]]
-
+or
 [TOC]
 ```
 
@@ -767,6 +769,8 @@ If a functionality is extended, the new option is listed as a sub-section.
 
 ### Blockquotes
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#blockquotes).
+
 Use a blockquote to highlight information, such as a side note. It's generated
 by starting the lines of the blockquote with `>`:
 
@@ -788,7 +792,7 @@ Quote break.
 
 #### Multiline blockquote
 
-If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#multiline-blockquote).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#multiline-blockquote).
 
 GitLab Flavored Markdown extends the standard Markdown by also supporting multi-line blockquotes
 fenced by `>>>`, with a blank line before and after the block:
@@ -819,6 +823,8 @@ trigger this problem.
 
 ### Code spans and blocks
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#code-spans-and-blocks).
+
 You can highlight anything that should be viewed as code and not standard text.
 
 Inline code is highlighted with single backticks `` ` ``:
@@ -880,8 +886,7 @@ Tildes are OK too.
 
 #### Colored code and syntax highlighting
 
-If this section isn't rendered correctly,
-[view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#colored-code-and-syntax-highlighting).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#colored-code-and-syntax-highlighting).
 
 GitLab uses the [Rouge Ruby library](https://github.com/rouge-ruby/rouge) for more colorful syntax
 highlighting in code blocks. For a list of supported languages visit the
@@ -945,6 +950,8 @@ But let's throw in a <b>tag</b>.
 
 ### Emphasis
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#emphasis).
+
 In Markdown, you can emphasize text in multiple ways. You can italicize, bold, strikethrough,
 and combine these emphasis styles together.
 Strikethrough is not part of the core Markdown standard, but is part of GitLab Flavored Markdown.
@@ -975,8 +982,7 @@ Strikethrough with double tildes. ~~Scratch this.~~
 
 #### Multiple underscores in words and mid-word emphasis
 
-If this section isn't rendered correctly,
-[view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#multiple-underscores-in-words).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#multiple-underscores-in-words).
 
 Avoid italicizing a portion of a word, especially when you're
 dealing with code and names that often appear with multiple underscores.
@@ -1017,6 +1023,8 @@ do*this*and*do*that*and*another thing
 
 ### Footnotes
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#footnotes).
+
 Footnotes add a link to a note rendered at the end of a Markdown file.
 
 To make a footnote, you need both a reference tag and a separate line (anywhere in the file) with
@@ -1061,9 +1069,11 @@ These are used to force the Vale ReferenceLinks check to skip these examples.
 #### H4
 ##### H5
 ###### H6
+```
 
-Alternatively, for H1 and H2, an underline-ish style:
+Alternatively, for H1 and H2, an underline style:
 
+```markdown
 Alt-H1
 ======
 
@@ -1073,6 +1083,8 @@ Alt-H2
 
 #### Header IDs and links
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#header-ids-and-links).
+
 GitLab Flavored Markdown extends the standard Markdown standard so that all Markdown-rendered headers automatically
 get IDs, which can be linked to, except in comments.
 
@@ -1113,69 +1125,77 @@ emoji is converted to an image, which is then removed from the ID.
 
 ### Horizontal Rule
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#horizontal-rule).
+
 Create a horizontal rule by using three or more hyphens, asterisks, or underscores:
 
 ```markdown
-Three or more hyphens,
-
 ---
 
-asterisks,
-
 ***
 
-or underscores
-
 ___
 ```
 
+---
+
+---
+
+---
+
 ### Images
 
-Examples:
+Embed images using inline or reference links.
+To see title text, hover over the image.
 
 <!--
-The following codeblock uses HTML to skip the Vale ReferenceLinks test.
-Do not change it back to a markdown codeblock.
+The following examples use HTML to skip the Vale ReferenceLinks test.
+Do not change it back to a markdown codeblocks.
 -->
 
-<!-- markdownlint-disable proper-names -->
+<!--
+DO NOT change the name of markdown_logo.png. This file is used for a test in
+spec/controllers/help_controller_spec.rb.
+-->
 
-<pre class="highlight"><code>Inline-style (hover to see title text):
+<!--
+The examples below use an in-line link to pass the Vale ReferenceLinks test.
+Do not change to a reference style link.
+-->
 
-![alt text](img/markdown_logo.png "Title Text")
+Inline-style:
 
-Reference-style (hover to see title text):
+<!-- markdownlint-disable proper-names -->
 
-![alt text1][logo]
+<pre class="highlight"><code>
+
+![alt text](img/markdown_logo.png "Title Text")
 
-&#91;logo]: img/markdown_logo.png "Title Text"
 </code></pre>
 
-<!-- markdownlint-enable proper-names -->
+![alt text](img/markdown_logo.png "Title Text")
 
-<!--
-DO NOT change the name of markdown_logo.png. This file is used for a test in
-spec/controllers/help_controller_spec.rb.
--->
+Reference-style:
 
-Inline-style (hover to see title text):
+<pre class="highlight"><code>
 
-![alt text](img/markdown_logo.png "Title Text")
+![alt text1][logo]
 
-Reference-style (hover to see title text):
+&#91;logo]: img/markdown_logo.png "Title Text"
 
-<!--
-The example below uses an in-line link to pass the Vale ReferenceLinks test.
-Do not change to a reference style link.
--->
+</code></pre>
 
 ![alt text](img/markdown_logo.png "Title Text")
 
+<!-- markdownlint-enable proper-names -->
+
 #### Change the image or video dimensions
 
 > - Support for images [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/28118) in GitLab 15.7.
 > - Support for videos [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/17139) in GitLab 15.9.
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#change-the-image-or-video-dimensions).
+
 You can control the width and height of an image or video by following the image with
 an attribute list.
 The value must an integer with a unit of either `px` (default) or `%`.
@@ -1195,44 +1215,39 @@ You can also use the `img` HTML tag instead of Markdown and set its `height` and
 
 #### Videos
 
-If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#videos).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#videos).
 
 Image tags that link to files with a video extension are automatically converted to
 a video player. The valid video extensions are `.mp4`, `.m4v`, `.mov`, `.webm`, and `.ogv`:
 
-```markdown
-Here's a sample video:
+Here's an example video:
 
+```markdown
 ![Sample Video](img/markdown_video.mp4)
 ```
 
-Here's a sample video:
-
 ![Sample Video](img/markdown_video.mp4)
 
 #### Audio
 
-If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#audio).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#audio).
 
 Similar to videos, link tags for files with an audio extension are automatically converted to
 an audio player. The valid audio extensions are `.mp3`, `.oga`, `.ogg`, `.spx`, and `.wav`:
 
-```markdown
-Here's a sample audio clip:
+Here's an example audio clip:
 
+```markdown
 ![Sample Audio](img/markdown_audio.mp3)
 ```
 
-Here's a sample audio clip:
-
 ![Sample Audio](img/markdown_audio.mp3)
 
 ### Inline HTML
 
 > Allowing `rel="license"` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/20857) in GitLab 14.6.
 
-To see the second example of Markdown rendered in HTML,
-[view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#inline-html).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#inline-html).
 
 You can also use raw HTML in your Markdown, and it usually works pretty well.
 
@@ -1297,8 +1312,7 @@ Markdown is fine in GitLab.
 
 #### Collapsible section
 
-To see the second Markdown example rendered in HTML,
-[view it in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#details-and-summary).
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#details-and-summary).
 
 Content can be collapsed using HTML's [`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details)
 and [`<summary>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary)
@@ -1363,6 +1377,8 @@ These details <em>remain</em> <b>hidden</b> until expanded.
 
 ### Line breaks
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#line-breaks).
+
 A line break is inserted (a new paragraph starts) if the previous text is
 ended with two newlines, like when you press <kbd>Enter</kbd> twice in a row. If you only
 use one newline (press <kbd>Enter</kbd> once), the next sentence remains part of the
@@ -1414,6 +1430,8 @@ A new line due to the previous backslash.
 
 ### Links
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#links).
+
 You can create links two ways: inline-style and reference-style. For example:
 
 <!--
@@ -1475,6 +1493,8 @@ points the link to `wikis/style` only when the link is inside of a wiki Markdown
 
 #### URL auto-linking
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#url-auto-linking).
+
 GitLab Flavored Markdown auto-links almost any URL you put into your text:
 
 ```markdown
@@ -1496,8 +1516,11 @@ GitLab Flavored Markdown auto-links almost any URL you put into your text:
 - <http://localhost:3000>
 
 <!-- vale gitlab.Spelling = YES -->
+
 ### Lists
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#lists).
+
 You can create ordered and unordered lists.
 
 For an ordered list, add the number you want the list
@@ -1653,6 +1676,8 @@ CommonMark ignores the blank line and renders this as one list with paragraph sp
 
 ### Superscripts / Subscripts
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#superscripts-subscripts).
+
 CommonMark and GitLab Flavored Markdown don't support the Redcarpet superscript syntax ( `x^2` ).
 Use the standard HTML syntax for superscripts and subscripts:
 
@@ -1670,6 +1695,8 @@ while the equation for the theory of relativity is E = mc<sup>2</sup>.
 
 ### Keyboard HTML tag
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#keyboard-html-tag).
+
 The `<kbd>` element is used to identify text that represents user keyboard input. Text surrounded by `<kbd>` tags is typically displayed in the browser's default monospace font.
 
 ```html
@@ -1680,6 +1707,8 @@ Press <kbd>Enter</kbd> to go to the next page.
 
 ### Tables
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#tables-1).
+
 Tables are not part of the core Markdown specification, but are part of GitLab Flavored Markdown.
 
 - The first line contains the headers, separated by "pipes" (`|`).
@@ -1716,6 +1745,8 @@ Example:
 
 #### Alignment
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#alignment).
+
 Additionally, you can choose the alignment of text in columns by adding colons (`:`)
 to the sides of the "dash" lines in the second row. This affects every cell in the column:
 
@@ -1736,6 +1767,8 @@ the headers are always left-aligned in Chrome and Firefox, and centered in Safar
 
 #### Cells with multiple lines
 
+[View this topic in GitLab](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/markdown.md#cells-with-multiple-lines).
+
 You can use HTML formatting to adjust the rendering of tables. For example, you can
 use `<br>` tags to force a cell to have multiple lines:
 
diff --git a/doc/user/project/integrations/webhooks.md b/doc/user/project/integrations/webhooks.md
index 33da78191c0..ccf416fc8c6 100644
--- a/doc/user/project/integrations/webhooks.md
+++ b/doc/user/project/integrations/webhooks.md
@@ -1,6 +1,7 @@
 ---
 stage: Manage
 group: Import and Integrate
+description: Custom HTTP callbacks, used to send events.
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
diff --git a/doc/user/project/repository/code_suggestions/index.md b/doc/user/project/repository/code_suggestions/index.md
index 2315778e0f2..ed9eeac1c2c 100644
--- a/doc/user/project/repository/code_suggestions/index.md
+++ b/doc/user/project/repository/code_suggestions/index.md
@@ -70,12 +70,12 @@ The editor supports these languages:
 | Google SQL       | **{dotted-circle}** No | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | Java             | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | JavaScript       | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
-| Kotlin           | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
+| Kotlin           | **{check-circle}** Yes (Requires third-party extension providing Kotlin support) | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | PHP              | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | Python           | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | Ruby             | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | Rust             | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
-| Scala            | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
+| Scala            | **{check-circle}** Yes (Requires third-party extension providing Scala support) | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | Swift            | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | TypeScript       | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes | **{check-circle}** Yes |
 | Terraform        | **{check-circle}** Yes (Requires third-party extension providing Terraform support) | **{check-circle}** Yes | **{dotted-circle}** No | **{check-circle}** Yes (Requires third-party extension providing the `terraform` file type) |