Merge branch 'selhorn-menu-updates-13' into 'master'

Updated Menu to Main menu

See merge request gitlab-org/gitlab!97883

doc/user/project/merge_requests/cherry_pick_changes.md

@@ -51,7 +51,7 @@ Commit `G` is added after the cherry-pick.
 After a merge request is merged, you can cherry-pick all changes introduced
 by the merge request:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**, and find your merge request.
 1. Scroll to the merge request reports section, and find the **Merged by** report.
 1. In the top right, select **Cherry-pick**:
@@ -69,7 +69,7 @@ You can cherry-pick a single commit from multiple locations in your GitLab proje
 
 To cherry-pick a commit from the list of all commits for a project:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Repository > Commits**.
 1. Select the title of the commit you want to cherry-pick.
 1. In the modal window, select the project and branch to cherry-pick into.
@@ -82,7 +82,7 @@ You can cherry-pick commits from any merge request in your project, regardless o
 whether the merge request is open or closed. To cherry-pick a commit from the
 list of commits included in a merge request:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**, and find your merge request.
 1. In the merge request's secondary menu, select **Commits** to display the commit details page.
 1. Select the title of the commit you want to cherry-pick.
@@ -96,7 +96,7 @@ list of commits included in a merge request:
 You can cherry-pick from the list of previous commits affecting an individual file
 when you view that file in your project's Git repository:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Repository > Files** and go to the file
    changed by the commit.
 1. Select **History**, then select the title of the commit you want to cherry-pick.

doc/user/project/merge_requests/commit_templates.md

@@ -29,7 +29,7 @@ Prerequisite:
 
 To do this:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > Merge requests**.
 1. Depending on the type of template you want to create, scroll to either
    [**Merge commit message template**](#default-template-for-merge-commits) or

doc/user/project/merge_requests/creating_merge_requests.md

@@ -14,7 +14,7 @@ There are many different ways to create a merge request.
 
 You can create a merge request from the list of merge requests.
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left menu, select **Merge requests**.
 1. In the top right, select **New merge request**.
 1. Select a source and target branch and then **Compare branches and continue**.
@@ -43,7 +43,7 @@ You can create a merge request when you add, edit, or upload a file to a reposit
 
 You can create a merge request when you create a branch.
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left menu, select **Repository > Branches**.
 1. Type a branch name and select **New branch**.
 1. Above the file list, on the right side, select **Create merge request**.
@@ -90,7 +90,7 @@ to reduce the need for editing merge requests manually through the UI.
 
 You can create a merge request from your fork to contribute back to the main project.
 
-1. On the top bar, select **Menu > Project**.
+1. On the top bar, select **Main menu > Project**.
 1. Select your fork of the repository.
 1. On the left menu, go to **Merge requests**, and select **New merge request**.
 1. In the **Source branch** drop-down list box, select the branch in your forked repository as the source branch.
@@ -120,7 +120,7 @@ Prerequisites:
 
 To create a merge request by sending an email:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left menu, select **Merge requests**.
 1. In the top right, select **Email a new merge request to this project**.
    An email address is displayed. Copy this address.
@@ -165,7 +165,7 @@ scenarios when you create a new merge request:
 To have merge requests from a fork by default target your own fork
 (instead of the upstream project), you can change the default.
 
-1. On the top bar, select **Menu > Project**.
+1. On the top bar, select **Main menu > Project**.
 1. On the left menu, select **Settings > General > Merge requests**.
 1. In the **Target project** section, select the option you want to use for
    your default target project.

doc/user/project/merge_requests/csv_export.md

@@ -12,7 +12,7 @@ Export all the data collected from a project's merge requests into a comma-separ
 
 To export merge requests to a CSV file:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** .
 1. Add any searches or filters. This can help you keep the size of the CSV file under the 15MB limit. The limit ensures
    the file can be emailed to a variety of email providers.

doc/user/project/merge_requests/dependencies.md

@@ -57,7 +57,7 @@ information about the dependency:
 
 To view dependency information on a merge request:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** and identify your merge request.
 1. Scroll to the merge request reports area. Dependent merge requests display information
    about the total number of dependencies set, such as
@@ -105,7 +105,7 @@ Prerequisite:
 
 To do this:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** and identify your merge request.
 1. Select **Edit**.
 1. In **Merge request dependencies**, paste either the reference or the full URL
@@ -120,7 +120,7 @@ Prerequisite:
 
 - You must have a role in the project that allows you to edit merge requests.
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** and identify your merge request.
 1. Select **Edit**.
 1. Scroll to **Merge request dependencies** and select **Remove** next to the reference

doc/user/project/merge_requests/index.md

@@ -27,7 +27,7 @@ You can view merge requests for your project, group, or yourself.
 
 To view all merge requests for a project:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**.
 
 Or, to use a [keyboard shortcut](../../shortcuts.md), press <kbd>g</kbd> + <kbd>m</kbd>.
@@ -36,7 +36,7 @@ Or, to use a [keyboard shortcut](../../shortcuts.md), press <kbd>g</kbd> + <kbd>
 
 To view merge requests for all projects in a group:
 
-1. On the top bar, select **Menu > Groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Merge requests**.
 
 If your group contains subgroups, this view also displays merge requests from the subgroup projects.
@@ -166,7 +166,7 @@ To assign the merge request to someone else, use the `/assign @user`
 [quick action](../quick_actions.md#issues-merge-requests-and-epics) in a text area in
 a merge request, or:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** and find your merge request.
 1. On the right sidebar, expand the right sidebar and locate the **Assignees** section.
 1. Select **Edit**.
@@ -186,7 +186,7 @@ accountable for it:
 To assign multiple assignees to a merge request, use the `/assign @user`
 [quick action](../quick_actions.md#issues-merge-requests-and-epics) in a text area, or:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** and find your merge request.
 1. On the right sidebar, expand the right sidebar and locate the **Assignees** section.
 1. Select **Edit** and, from the dropdown list, select all users you want

doc/user/project/merge_requests/merge_when_pipeline_succeeds.md

@@ -34,7 +34,7 @@ To do this when pushing from the command line, use the `merge_request.merge_when
 
 To do this from the GitLab user interface:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**.
 1. Scroll to the merge request reports section.
 1. Optional. Select your desired merge options, such as **Delete source branch**,
@@ -57,7 +57,7 @@ Prerequisites:
 
 To do this:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**.
 1. Scroll to the merge request reports section.
 1. Select **Cancel auto-merge**.
@@ -83,7 +83,7 @@ Prerequisites:
 
 To enable this setting:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > Merge requests**.
 1. Scroll to **Merge checks**, and select **Pipelines must succeed**.
    This setting also prevents merge requests from being merged if there is no pipeline,
@@ -104,7 +104,7 @@ Prerequisite:
 
 To change this behavior:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Merge requests**.
 1. Under **Merge checks**:

doc/user/project/merge_requests/methods/index.md

@@ -12,7 +12,7 @@ merge requests are merged into an existing branch.
 
 ## Configure a project's merge method
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > Merge requests**.
 1. In the **Merge method** section, select your desired merge method.
 1. Select **Save changes**.

doc/user/project/merge_requests/revert_changes.md

@@ -30,7 +30,7 @@ Prerequisites:
 
 To do this:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests** and identify your merge request.
 1. Scroll to the merge request reports area, and find the report showing when the
    merge request was merged.
@@ -55,7 +55,7 @@ Prerequisites:
 
 To do this:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. If you know the merge request that contains the commit:
    1. On the left sidebar, select **Merge requests** and identify your merge request.
    1. Select **Commits**, then select the title of the commit you want to revert. GitLab displays the contents of the commit.

doc/user/project/merge_requests/squash_and_merge.md

@@ -60,7 +60,7 @@ squash the commits as part of the merge process:
 
 To configure the default squashing behavior for all merge requests in your project:
 
-1. On the top bar, select **Menu > Projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > Merge requests**.
 1. In the **Squash commits when merging** section, select your desired behavior:
    - **Do not allow**: Squashing is never performed, and the option is not displayed.