Add latest changes from gitlab-org/gitlab@master

3 files changed, 78 insertions, 78 deletions

diff --git a/data/whats_new/202206220001_15_1.yml b/data/whats_new/202206220001_15_1.yml
index ab91ffeecb6..4a57db233b9 100644
--- a/data/whats_new/202206220001_15_1.yml
+++ b/data/whats_new/202206220001_15_1.yml
@@ -17,7 +17,7 @@
   gitlab-com: true
   available_in: [Premium, Ultimate]
   documentation_link: https://docs.gitlab.com/ee/user/group/saml_sso/group_sync.html
-  image_url: https://about.gitlab.com/images/15_1/SAML_Group_Sync.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  image_url: https://about.gitlab.com/images/15_1/SAML_Group_Sync.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
   published_at: 2022-06-22
   release: 15.1
 - name: Enhancing visibility into Value Stream with DORA metrics
@@ -28,7 +28,7 @@
   gitlab-com: true
   available_in: [Free, Premium, Ultimate]
   documentation_link: https://docs.gitlab.com/ee/user/analytics/ci_cd_analytics.html
-  image_url: https://about.gitlab.com/images/15_1/vsa_dora_n_ttrs.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  image_url: https://about.gitlab.com/images/15_1/vsa_dora_n_ttrs.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
   published_at: 2022-06-22
   release: 15.1
 - name: "SLSA-2 attestation included for build artifacts"
diff --git a/data/whats_new/202207220001_15_2.yml b/data/whats_new/202207220001_15_2.yml
index 4f6f65c9f18..7563a9ffbe9 100644
--- a/data/whats_new/202207220001_15_2.yml
+++ b/data/whats_new/202207220001_15_2.yml
@@ -1,4 +1,4 @@
-- name: "Live preview diagrams in the wiki WYSIWYG editor" # Match the release post entry
+- name: "Live preview diagrams in the wiki WYSIWYG editor"  # Match the release post entry
   description: | # Do not modify this line, instead modify the lines below.
     GitLab Flavored Markdown includes extensions to support [Mermaid, PlantUML, and Kroki diagrams](https://docs.gitlab.com/ee/user/markdown.html#diagrams-and-flowcharts) but writing anything other than the most basic diagrams can be cumbersome without a live preview. You can toggle between the raw source and static preview and there are external tools you can use to write these diagrams, but the shift away from your content can be distracting.
 
@@ -11,8 +11,8 @@
   image_url: https://about.gitlab.com/images/15_2/create-preview-diagrams-in-wysiwyg.png
   published_at: 2022-07-22
   release: 15.2
-- name: Incident timeline # Match the release post entry
-  description: | # Do not modify this line, instead modify the lines below.
+- name: Incident timeline  # Match the release post entry
+  description: |  # Do not modify this line, instead modify the lines below.
     Capturing what happened during an incident is an important practice that facilitates learning and the opportunity for improvement. Yet, asking incident responders to take on additional administrative tasks when they're busy fire-fighting, or trying to reconstruct the timeline of events post incident lead to incomplete or less than accurate information.
 
     GitLab incident timeline is designed to make information capture during an incident, or post incident, easy and efficient. In the Incident timeline MVC, we make it possible to add new timeline events manually, delete a timeline event, and view the incident timeline in a dedicated tab within an incident issue.
@@ -24,8 +24,8 @@
   image_url: https://img.youtube.com/vi/a0brUwOajvQ/hqdefault.jpg
   published_at: 2022-07-22
   release: 15.2
-- name: "Merge request reports redesign" # Match the release post entry
-  description: | # Do not modify this line, instead modify the lines below.
+- name: "Merge request reports redesign"  # Match the release post entry
+  description: |  # Do not modify this line, instead modify the lines below.
     Merge request reports are an important part of code review, providing insights into the impact of changes and improvements to meet project standards.
 
     Report widgets now all follow design guidelines for layout, hierarchy, and content sections, making them consistent, scannable, and utilitarian. These improvements make it easier for you to find actionable information in each report.
@@ -37,8 +37,8 @@
   image_url: https://about.gitlab.com/images/15_2/create-merge-request-widget-redesign.png
   published_at: 2022-07-22
   release: 15.2
-- name: "Change failure rate chart for visualizing software stability" # Match the release post entry
-  description: | # Do not modify this line, instead modify the lines below.
+- name: "Change failure rate chart for visualizing software stability"  # Match the release post entry
+  description: |  # Do not modify this line, instead modify the lines below.
     In this release, we added a new trend chart for the DORA [Change failure rate](https://docs.gitlab.com/ee/user/analytics/ci_cd_analytics.html) metric. This chart shows the percentage of deployments that cause an incident in a production environment. GitLab measures the change failure rate as the number of [incidents](https://docs.gitlab.com/ee/operations/incident_management/incidents.html) divided by the number of deployments to a production environment during a given time period.
 
     This is the fourth DORA chart available in GitLab that provides insights into [value stream velocity and reliability trends](https://about.gitlab.com/blog/2022/06/20/gitlab-value-stream-management-and-dora/).
@@ -50,8 +50,8 @@
   image_url: https://about.gitlab.com/images/15_2/dora4_chart_cfr.png
   published_at: 2022-07-22
   release: 15.2
-- name: "Enforce IP address restrictions for Git over SSH" # Match the release post entry
-  description: | # Do not modify this line, instead modify the lines below.
+- name: "Enforce IP address restrictions for Git over SSH"  # Match the release post entry
+  description: |  # Do not modify this line, instead modify the lines below.
       Limiting access to requests from a trusted set of IP addresses may improve security. Until now, only the API and UI supported such access restrictions; SSH access was blocked entirely. SSH now also adheres to this restriction, and grants access only to requests coming from IP addresses in your list.
   stage: create
   self-managed: false
@@ -61,8 +61,8 @@
   image_url: https://img.youtube.com/vi/f60EgVK3mWc/hqdefault.jpg
   published_at: 2022-07-22
   release: 15.2
-- name: "Group and subgroup scan execution policies" # Match the release post entry
-  description: | # Do not modify this line, instead modify the lines below.
+- name: "Group and subgroup scan execution policies"  # Match the release post entry
+  description: |  # Do not modify this line, instead modify the lines below.
     Your security and compliance teams can now apply policies uniformly to all projects by scanning execution policies at the group and subgroup levels. This functionality is especially helpful for large organizations who have a large number of projects. Policies defined for the group or subgroup will flow down and apply to all child projects. To get started, ask your group owner to link a security policy project to your group on the **Security & Compliance > Policies** page.
 
     Currently scan execution policies are the only policy type that is supported at the group and subgroup levels. You can track the efforts to add group and subgroup level support for scan result policies in [this epic](https://gitlab.com/groups/gitlab-org/-/epics/7622).
@@ -74,8 +74,8 @@
   image_url: https://about.gitlab.com/images/15_2/protect_group_policies.png
   published_at: 2022-07-22
   release: 15.2
-- name: "Set the image pull policy in pipeline configuration" # Match the release post entry
-  description: | # Do not modify this line, instead modify the lines below.
+- name: "Set the image pull policy in pipeline configuration"  # Match the release post entry
+  description: |  # Do not modify this line, instead modify the lines below.
     You can select different [pull policies](https://docs.gitlab.com/runner/executors/docker.html#how-pull-policies-work) for how a GitLab Runner downloads Docker images in CI/CD jobs. `always` (the default behavior) ensures the image is always downloaded, `if-not-present` downloads an image only when a local version does not exist, and `never` only uses the local version (never download an image).
 
     Previously, you could define the pull policy only at the runner level. In this release we've added the ability to define the pull policy at the pipeline level. Use `pull_policy` in your `.gitlab-ci.yml` to define different pull policies at the job or pipeline level. This feature is not supported by shared runners.
diff --git a/data/whats_new/202209220001_15_04.yml b/data/whats_new/202209220001_15_04.yml
index 056826c6457..3ee7c65ce23 100644
--- a/data/whats_new/202209220001_15_04.yml
+++ b/data/whats_new/202209220001_15_04.yml
@@ -1,19 +1,19 @@
-- name: "Suggested Reviewers open beta" # Match the release post entry
+- name: "Suggested Reviewers open beta"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     Deciding the right person to [review your merge request](https://docs.gitlab.com/ee/user/project/merge_requests/reviews/) isn't always straightforward or obvious. Choosing the wrong reviewer can cause delays, low quality reviews, back and forth reassigning reviewers, or even no review at all.
 
     Now, GitLab can recommend a reviewer with [Suggested Reviewers](https://docs.gitlab.com/ee/user/project/merge_requests/reviews/#suggested-reviewers). Using the changes in a merge request and a project's contribution graph, machine learning powered suggestions appear in the [reviewer dropdown](https://docs.gitlab.com/ee/user/project/merge_requests/getting_started.html#reviewer) in the merge request sidebar.
 
     This feature is currently in [beta](https://about.gitlab.com/handbook/product/gitlab-the-product/#open-beta) behind a [feature flag](https://gitlab.com/gitlab-org/gitlab/-/issues/368356). It will be rolling out to all Ultimate GitLab.com customers over the next week.
-  stage: create # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: false # Boolean value (true or false)
-  gitlab-com: true # Boolean value (true or false)
-  available_in: [Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/project/merge_requests/reviews/#suggested-reviewers' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://about.gitlab.com/images/15_4/create-code-review-suggested-reviewers.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
-- name: "Improved CI/CD integration in VS Code" # Match the release post entry
+  stage: create  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: false  # Boolean value (true or false)
+  gitlab-com: true  # Boolean value (true or false)
+  available_in: [Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://docs.gitlab.com/ee/user/project/merge_requests/reviews/#suggested-reviewers'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://about.gitlab.com/images/15_4/create-code-review-suggested-reviewers.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y
+- name: "Improved CI/CD integration in VS Code"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     When you're constructing complicated GitLab CI configurations that may contain `include:` or `extends:` keywords, it's challenging to ensure the configuration is valid and the resulting file has your expected configuration. Use [GitLab Workflow](https://marketplace.visualstudio.com/items?itemName=GitLab.gitlab-workflow) for Visual Studio Code to preview your merged GitLab CI/CD configuration file directly in VS Code. You can view your changes locally, and ensure your configuration is as you expect, before you commit and push.
 
@@ -21,28 +21,28 @@
 
      * Download artifacts: [commit `f4d027c`](https://gitlab.com/gitlab-org/gitlab-vscode-extension/commit/f4d027c616c884bef9fc42e5f20dfac43b811134), [merge request `!635`](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/merge_requests/635)
      * Retry or cancel an existing pipeline: [commit `c2caee4`](https://gitlab.com/gitlab-org/gitlab-vscode-extension/commit/c2caee40cfcbfb5d13cc790f9a2d1cfcf6c6a7ab), [merge request `!637`](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/merge_requests/637)
-  stage: create # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: true # Boolean value (true or false)
-  gitlab-com: false # Boolean value (true or false)
-  available_in: [Free, Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://gitlab.com/gitlab-org/gitlab-vscode-extension#show-merged-gitlab-cicd-configuration' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://about.gitlab.com/images/15_4/create-vs-code-cicd-improvements.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
-- name: "Users on verified domains can bypass email validation" # Match the release post entry
+  stage: create  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: true  # Boolean value (true or false)
+  gitlab-com: false  # Boolean value (true or false)
+  available_in: [Free, Premium, Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://gitlab.com/gitlab-org/gitlab-vscode-extension#show-merged-gitlab-cicd-configuration'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://about.gitlab.com/images/15_4/create-vs-code-cicd-improvements.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y
+- name: "Users on verified domains can bypass email validation"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     New GitLab users created using SAML or SCIM that belong to a [verified domain](https://docs.gitlab.com/ee/user/project/pages/custom_domains_ssl_tls_certification/#1-add-a-custom-domain) no longer receive the GitLab account verification e-mail.
 
     This reduces account activation friction. Accounts generated through a provisioning process are already verified, so users should not have to individually verify them manually.
-  stage: manage # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: false # Boolean value (true or false)
-  gitlab-com: true # Boolean value (true or false)
-  available_in: [Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/group/saml_sso/index.html#bypass-user-verification-with-verified-domains' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://about.gitlab.com/images/15_4/domain-verification.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
-- name: "Sortable, filterable data-driven tables in Markdown" # Match the release post entry
+  stage: manage  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: false  # Boolean value (true or false)
+  gitlab-com: true  # Boolean value (true or false)
+  available_in: [Premium, Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://docs.gitlab.com/ee/user/group/saml_sso/index.html#bypass-user-verification-with-verified-domains'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://about.gitlab.com/images/15_4/domain-verification.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y
+- name: "Sortable, filterable data-driven tables in Markdown"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     Working with tables in Markdown can be a bit cumbersome. Not only is it difficult to figure out the correct number of pipes and empty cells, but the table output is static when you save your document. If you have to sort the table by the third column in an ascending order, you end up rewriting the whole thing.
 
@@ -58,46 +58,46 @@
     - Dynamic filtering of data using `"filter" : true`
 
     Now it's as simple as a click when you have to re-sort that 100-row table and as easy as a web search when you have to find that one issue reference lost in a sea of nearly identical URLs.
-  stage: create # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: true # Boolean value (true or false)
-  gitlab-com: true # Boolean value (true or false)
-  available_in: [Free, Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/markdown.html#json' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://img.youtube.com/vi/12yWKw1AdKY/hqdefault.jpg # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
-- name: "Getting started with GitLab Pages just got easier" # Match the release post entry
+  stage: create  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: true  # Boolean value (true or false)
+  gitlab-com: true  # Boolean value (true or false)
+  available_in: [Free, Premium, Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://docs.gitlab.com/ee/user/markdown.html#json'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://img.youtube.com/vi/12yWKw1AdKY/hqdefault.jpg  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y
+- name: "Getting started with GitLab Pages just got easier"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     We've made it much easier to get started with GitLab Pages. Instead of creating configuration files by hand, build them interactively using the GitLab UI. Just answer a few basic questions on how your app is built, and we'll build the `.gitlab-ci.yml` file to get you started.
 
     This is the first time we're using our new [Pipeline Wizard](https://docs.gitlab.com/ee/development/cicd/pipeline_wizard.html), a tool that makes it easy to create `.gitlab-ci.yml` files by building them in the GitLab UI. You can look forward to more simplified onboarding helpers like this one.
-  stage: create # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: true # Boolean value (true or false)
-  gitlab-com: true # Boolean value (true or false)
-  available_in: [Free, Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/user/project/pages/getting_started/pages_ui.html' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://about.gitlab.com/images/15_4/create-pages-onboarding.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
-- name: "More powerful Linux machine types for GitLab SaaS runners" # Match the release post entry
+  stage: create  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: true  # Boolean value (true or false)
+  gitlab-com: true  # Boolean value (true or false)
+  available_in: [Free, Premium, Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://docs.gitlab.com/ee/user/project/pages/getting_started/pages_ui.html'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://about.gitlab.com/images/15_4/create-pages-onboarding.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y
+- name: "More powerful Linux machine types for GitLab SaaS runners"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     When you run jobs on GitLab SaaS Linux runners, you now have access to more powerful machine types: medium and large. With these two machine types, you have more choices for your GitLab SaaS CI/CD jobs. And with 100% job isolation on an ephemeral virtual machine, and security and autoscaling fully managed by GitLab, you can confidently run your critical CI/CD jobs on GitLab SaaS.
-  stage: create # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: false # Boolean value (true or false)
-  gitlab-com: true # Boolean value (true or false)
-  available_in: [Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/ci/runners/saas/linux_saas_runner.html' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://about.gitlab.com/images/15_4/select-multiple-gitlab-saas-linux-runners.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
-- name: "Limit the maximum number of custom domains per project" # Match the release post entry
+  stage: create  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: false  # Boolean value (true or false)
+  gitlab-com: true  # Boolean value (true or false)
+  available_in: [Premium, Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://docs.gitlab.com/ee/ci/runners/saas/linux_saas_runner.html'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://about.gitlab.com/images/15_4/select-multiple-gitlab-saas-linux-runners.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y
+- name: "Limit the maximum number of custom domains per project"  # Match the release post entry
   description: |  # Do not modify this line, instead modify the lines below.
     You can use GitLab Pages to define custom domains for your website. Too many custom domains, however, can result in slow response times from the Pages API and impact the overall reliability of the service. Now you can limit the maximum number of custom domains per project at the instance level and strike the right balance for your needs. The default value is `0` (unlimited).
-  stage: create # String value of the stage that the feature was created in. e.g., Growth
-  self-managed: true # Boolean value (true or false)
-  gitlab-com: false # Boolean value (true or false)
-  available_in: [Free, Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
-  documentation_link: 'https://docs.gitlab.com/ee/administration/pages/#set-maximum-number-of-gitlab-pages-custom-domains-for-a-project' # This is the documentation URL, but can be a URL to a video if there is one
-  image_url: https://about.gitlab.com/images/15_4/create-pages-domain-limits.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
-  published_at: 2022-09-22 # YYYY-MM-DD
-  release: 15.4 # XX.Y
+  stage: create  # String value of the stage that the feature was created in. e.g., Growth
+  self-managed: true  # Boolean value (true or false)
+  gitlab-com: false  # Boolean value (true or false)
+  available_in: [Free, Premium, Ultimate]  # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
+  documentation_link: 'https://docs.gitlab.com/ee/administration/pages/#set-maximum-number-of-gitlab-pages-custom-domains-for-a-project'  # This is the documentation URL, but can be a URL to a video if there is one
+  image_url: https://about.gitlab.com/images/15_4/create-pages-domain-limits.png  # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  published_at: 2022-09-22  # YYYY-MM-DD
+  release: 15.4  # XX.Y