Merge branch '442469-aqualls-add-metadata' into 'master'

Add description metadata for six Create files

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147946



Merged-by: Phillip Wells <pwells@gitlab.com>
Approved-by: Phillip Wells <pwells@gitlab.com>
Co-authored-by: Amy Qualls <aqualls@gitlab.com>

doc/api/branches.md

@@ -2,6 +2,7 @@
 stage: Create
 group: Source Code
 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"
+description: "Documentation for the REST API for Git branches in GitLab."
 ---
 
 # Branches API

doc/topics/git/rollback_commits.md

@@ -2,6 +2,7 @@
 stage: Create
 group: Source Code
 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
+description: "In Git, commits with problems can be undone, reset, or completely removed."
 ---
 
 # Roll back commits

doc/user/project/merge_requests/approvals/rules.md

@@ -2,6 +2,7 @@
 stage: Create
 group: Source Code
 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
+description: "Use approval rules to define the users or groups who should approve merge requests. Approvers can be optional or required."
 ---
 
 # Merge request approval rules

doc/user/project/merge_requests/cherry_pick_changes.md

@@ -2,6 +2,7 @@
 stage: Create
 group: Source Code
 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
+description: "Cherry-pick a Git commit when you want to add a single commit from one branch to another."
 ---
 
 # Cherry-pick changes

doc/user/project/repository/forking_workflow.md

@@ -2,6 +2,7 @@
 stage: Create
 group: Source Code
 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
+description: "Fork a Git repository when you want to contribute changes back to an upstream repository you don't have permission to contribute to directly."
 ---
 
 # Forks
@@ -73,7 +74,7 @@ or the command line. GitLab Premium and Ultimate tiers can also automate updates
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/330243) in GitLab 15.11 [with a flag](../../../administration/feature_flags.md) named `synchronize_fork`. Disabled by default, but enabled for projects in the `gitlab-org/gitlab` and `gitlab-com/www-gitlab-com` namespaces only.
 > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/330243) in GitLab 16.0. Feature flag `synchronize_fork` removed.
 
-Prerequisite:
+Prerequisites:
 
 - The fork must be created from an [unprotected branch](../protected_branches.md) in upstream repository.
 

doc/user/project/repository/push_rules.md

@@ -2,6 +2,7 @@
 stage: Create
 group: Source Code
 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"
+description: "Use push rules to control the content and format of Git commits your repository will accept. Set standards for commit messages, and block secrets or credentials from being added accidentally."
 ---
 
 # Push rules

doc/user/project/web_ide/index.md

@@ -2,6 +2,7 @@
 stage: Create
 group: IDE
 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
+description: "Use the Web IDE to edit multiple files in the GitLab UI, stage commits, and create merge requests."
 ---
 
 # Web IDE