From bb8d54ee23e014b36cf8e945be131a6d9437e167 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Mon, 13 Nov 2023 17:39:38 -0800 Subject: [PATCH 01/15] Udpated create MR tasks --- .../merge_requests/creating_merge_requests.md | 87 +++++++------------ 1 file changed, 32 insertions(+), 55 deletions(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index ec269bec84d552..bff0e988487965 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -7,78 +7,42 @@ description: "How to create merge requests in GitLab." # Creating merge requests **(FREE ALL)** -GitLab provides many different ways to create a merge request. +You can create a merge request on the GitLab UI, by email, or with Git commands. -NOTE: -GitLab enforces [branch naming rules](../repository/branches/index.md#name-your-branch) -to prevent problems, and provides -[branch naming patterns](../repository/branches/index.md#prefix-branch-names-with-issue-numbers) -to streamline merge request creation. +To create a merge request, you must follow the guide for branch names. For more information, see [Name your branch](https://docs.gitlab.com/ee/user/project/repository/branches/#name-your-branch). ## From the merge request list You can create a merge request from the list of merge requests. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Merge requests**. -1. In the upper-right corner, select **New merge request**. -1. Select a source and target branch and then **Compare branches and continue**. -1. Fill out the fields and select **Create merge request**. +1. In the upper-left corner, select **Create merge request**. +1. Complete the fields. +1. Select **Create merge request**. -NOTE: -Merge requests are designed around a one-to-one (1:1) branch relationship. Only one open merge request may -be associated with a given target branch at a time. +Merge requests follow a one-to-one branch relationship. Each target branch can have only one open merge request at a time. ## From an issue -> The **Create merge request** button [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/349566) to open the merge request creation form in GitLab 14.8. - -If your development workflow requires an issue for every merge -request, you can create a branch directly from the issue to speed the process up. -The new branch, and later its merge request, are marked as related to this issue. -After merging the merge request, the issue is closed automatically, unless -[automatic issue closing is disabled](../issues/managing_issues.md#disable-automatic-issue-closing). -You can see a **Create merge request** dropdown list below the issue description. - -NOTE: -In GitLab 14.8 and later, selecting **Create merge request** -[redirects to the merge request creation form](https://gitlab.com/gitlab-org/gitlab/-/issues/349566) -instead of immediately creating the merge request. - -**Create merge request** doesn't display if: - -- A branch with the same name already exists. -- A merge request already exists for this branch. -- Your project has an active fork relationship. -- Your project is private and the issue is confidential. +> Create merge requests redirects to the merge request creation form [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349566) in GitLab 14.8. -To make this button appear, one possible workaround is to -[remove your project's fork relationship](../repository/forking_workflow.md#unlink-a-fork). -After removal, the fork relationship cannot be restored. This project can no longer -be able to receive or send merge requests to the source project, or other forks. +Create a merge request and a branch from an issue. When you create a merge request from an issue, the new branch and merge request are marked as related to the issue. The issue automatically closes when the merge request is complete unless automatic issue closing is off. For more information, see [Disable automatic issue closing](../issues/managing_issues.md#disable-automatic-issue-closing). -The dropdown list contains the options **Create merge request and branch** and **Create branch**. +To create a branch and merge request from an issue: -After selecting one of these options, a new branch or branch and merge request -is created based on your project's [default branch](../repository/branches/default.md). -The branch name is based on your project's [branch name template](../repository/branches/index.md), -but this value can be changed. +Prerequisites: -When you select **Create branch** in an empty -repository project, GitLab performs these actions: +- You must have at least the Developer role for the project. -- Creates a default branch. -- Commits a blank `README.md` file to it. -- Creates and redirects you to a new branch based on the issue title. -- _If your project is [configured with a deployment service](../integrations/index.md) like Kubernetes,_ - GitLab prompts you to set up [auto deploy](../../../topics/autodevops/stages.md#auto-deploy) - by helping you create a `.gitlab-ci.yml` file. +To create a merge request and branch from an issue: -After the branch is created, you can edit files in the repository to fix -the issue. When a merge request is created based on the newly-created branch, -the description field displays the [issue closing pattern](../issues/managing_issues.md#closing-issues-automatically) -`Closes #ID`, where `ID` is the ID of the issue. This closes the issue when the -merge request is merged. +1. On the left sidebar, select ***Search or go to*** and find your project. +1. Select ***Issues*** and find your issue. +1. From the **Create merge request** dropdown list, select **Create merge request and branch**. You can use the default branch name, or create a different name. +1. Select **Create merge request**. +1. Complete the fields. +1. Select **Create merge request* +When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). ## When you add, edit, or upload a file @@ -221,3 +185,16 @@ To have merge requests from a fork by default target your own fork 1. In the **Target project** section, select the option you want to use for your default target project. 1. Select **Save changes**. + +## Troubleshooting + +You might not find the **Create merge request** option on your issue page. + +Create merge request will not display if: + +- A branch with the same name already exists. +- A merge request already exists for this branch. +- Your project has an active fork relationship. +- Your project is private and the issue is confidential. + +To restore **Create merge request** on your issue page, you can remove your project's fork relationship. Aftter you remove a fork relationship, you cannot send merge requests from your project to the source project. For more information on fork relationship removal, see [Unlink a fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#unlink-a-fork). -- GitLab From 5dce46725350fac23e84a4593cf7fb9be101af01 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Mon, 13 Nov 2023 23:53:32 +0000 Subject: [PATCH 02/15] Update creating_merge_requests.md --- doc/user/project/merge_requests/creating_merge_requests.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index bff0e988487965..66b00c68d9239b 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -28,8 +28,6 @@ Merge requests follow a one-to-one branch relationship. Each target branch can h Create a merge request and a branch from an issue. When you create a merge request from an issue, the new branch and merge request are marked as related to the issue. The issue automatically closes when the merge request is complete unless automatic issue closing is off. For more information, see [Disable automatic issue closing](../issues/managing_issues.md#disable-automatic-issue-closing). -To create a branch and merge request from an issue: - Prerequisites: - You must have at least the Developer role for the project. -- GitLab From fc3cbec3fc9ea85458683b715d0ece2f47e6c76b Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Mon, 13 Nov 2023 23:53:54 +0000 Subject: [PATCH 03/15] Update creating_merge_requests.md --- doc/user/project/merge_requests/creating_merge_requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 66b00c68d9239b..027196d82ced85 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -35,7 +35,7 @@ Prerequisites: To create a merge request and branch from an issue: 1. On the left sidebar, select ***Search or go to*** and find your project. -1. Select ***Issues*** and find your issue. +1. Select **Issues** and find your issue. 1. From the **Create merge request** dropdown list, select **Create merge request and branch**. You can use the default branch name, or create a different name. 1. Select **Create merge request**. 1. Complete the fields. -- GitLab From df81f09a28300e70b36c874a9236317c3f5793df Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Mon, 13 Nov 2023 23:54:21 +0000 Subject: [PATCH 04/15] Update creating_merge_requests.md --- doc/user/project/merge_requests/creating_merge_requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 027196d82ced85..8d7f0d21cb7e82 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -34,7 +34,7 @@ Prerequisites: To create a merge request and branch from an issue: -1. On the left sidebar, select ***Search or go to*** and find your project. +1. On the left sidebar, select **Search or go to** and find your project. 1. Select **Issues** and find your issue. 1. From the **Create merge request** dropdown list, select **Create merge request and branch**. You can use the default branch name, or create a different name. 1. Select **Create merge request**. -- GitLab From d60c14a52f99fae9ebf3a02eba4fa245fe0b46e1 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Mon, 13 Nov 2023 23:55:26 +0000 Subject: [PATCH 05/15] Update creating_merge_requests.md --- doc/user/project/merge_requests/creating_merge_requests.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 8d7f0d21cb7e82..877e5f7373d923 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -39,7 +39,8 @@ To create a merge request and branch from an issue: 1. From the **Create merge request** dropdown list, select **Create merge request and branch**. You can use the default branch name, or create a different name. 1. Select **Create merge request**. 1. Complete the fields. -1. Select **Create merge request* +1. Select **Create merge request**. + When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). ## When you add, edit, or upload a file -- GitLab From b183b658d37fbd450882be1488de00208543e2ec Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 14 Nov 2023 16:21:21 +0000 Subject: [PATCH 06/15] Changed hyperlink to relative link --- doc/user/project/merge_requests/creating_merge_requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 877e5f7373d923..b15e00a8b05d94 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -9,7 +9,7 @@ description: "How to create merge requests in GitLab." You can create a merge request on the GitLab UI, by email, or with Git commands. -To create a merge request, you must follow the guide for branch names. For more information, see [Name your branch](https://docs.gitlab.com/ee/user/project/repository/branches/#name-your-branch). +To create a merge request, you must follow the guide for branch names. For more information, see [Name your branch](../user/project/repository/branches.md#name-your-branch) ## From the merge request list -- GitLab From cc3d7974efad660fb4d22741fc54109dd45d2e55 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 14 Nov 2023 16:22:37 +0000 Subject: [PATCH 07/15] Attempt two --- doc/user/project/merge_requests/creating_merge_requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index b15e00a8b05d94..2ec27bc77a891c 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -9,7 +9,7 @@ description: "How to create merge requests in GitLab." You can create a merge request on the GitLab UI, by email, or with Git commands. -To create a merge request, you must follow the guide for branch names. For more information, see [Name your branch](../user/project/repository/branches.md#name-your-branch) +To create a merge request, you must follow the guide for branch names. For more information, see [Name your branch](../user/project/repository/branches.md#name-your-branch). ## From the merge request list -- GitLab From 16741b2136edd522c205c368d295e277e6ffc743 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 14 Nov 2023 14:21:58 -0800 Subject: [PATCH 08/15] Fix broken pipeline link --- doc/user/project/merge_requests/creating_merge_requests.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 2ec27bc77a891c..b6cb06405866ba 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -9,7 +9,7 @@ description: "How to create merge requests in GitLab." You can create a merge request on the GitLab UI, by email, or with Git commands. -To create a merge request, you must follow the guide for branch names. For more information, see [Name your branch](../user/project/repository/branches.md#name-your-branch). +To create a merge request, you must follow the branch name guide. For more information on branch name rules, see [Name your branch](../repository/branches.md#name-your-branch). ## From the merge request list @@ -43,6 +43,8 @@ To create a merge request and branch from an issue: When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). +You can also begin your Git branch name with the issue number and a hyphen to link a merge request to an issue. For more information, see [Prefix branch names with issue numbers](../repository/branches.md#prefix-branch-names-with-issue-numbers). + ## When you add, edit, or upload a file You can create a merge request when you add, edit, or upload a file to a repository. -- GitLab From 91dd2c98f625739a39df55fc6bf63ac6ab068ff5 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 14 Nov 2023 14:34:13 -0800 Subject: [PATCH 09/15] Updated steps again --- doc/user/project/merge_requests/creating_merge_requests.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index b6cb06405866ba..fcd31a31ccc927 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -16,7 +16,10 @@ To create a merge request, you must follow the branch name guide. For more infor You can create a merge request from the list of merge requests. 1. On the left sidebar, select **Search or go to** and find your project. -1. In the upper-left corner, select **Create merge request**. +1. Select **Merge requests**. +1. In the upper-left corner, select **New merge request**. +1. Complete the fields. +1. Select **Compare branches and continue**. 1. Complete the fields. 1. Select **Create merge request**. -- GitLab From bc2c26b1ca76f5a176b517cb1ad00d4dac06814c Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 14 Nov 2023 15:10:18 -0800 Subject: [PATCH 10/15] Attempt to correct link again --- doc/user/project/merge_requests/creating_merge_requests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index fcd31a31ccc927..d219c5d7d9f1a3 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -9,7 +9,7 @@ description: "How to create merge requests in GitLab." You can create a merge request on the GitLab UI, by email, or with Git commands. -To create a merge request, you must follow the branch name guide. For more information on branch name rules, see [Name your branch](../repository/branches.md#name-your-branch). +To create a merge request, you must follow the branch name guide. For more information on branch name rules, see [Name your branch](../repository/branches/index.md#name-your-branch). ## From the merge request list @@ -46,7 +46,7 @@ To create a merge request and branch from an issue: When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). -You can also begin your Git branch name with the issue number and a hyphen to link a merge request to an issue. For more information, see [Prefix branch names with issue numbers](../repository/branches.md#prefix-branch-names-with-issue-numbers). +You can also begin your Git branch name with the issue number and a hyphen to link a merge request to an issue. For more information, see [Prefix branch names with issue numbers](../repository/branches/index.md#prefix-branch-names-with-issue-numbers). ## When you add, edit, or upload a file -- GitLab From 3e8b6a69ffbe9cbd94012cc67b490887cc2a6bfa Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 14 Nov 2023 15:30:31 -0800 Subject: [PATCH 11/15] Updated link --- doc/user/project/merge_requests/creating_merge_requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index d219c5d7d9f1a3..3abb96f2df398c 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -201,4 +201,4 @@ Create merge request will not display if: - Your project has an active fork relationship. - Your project is private and the issue is confidential. -To restore **Create merge request** on your issue page, you can remove your project's fork relationship. Aftter you remove a fork relationship, you cannot send merge requests from your project to the source project. For more information on fork relationship removal, see [Unlink a fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#unlink-a-fork). +To restore **Create merge request** on your issue page, you can remove your project's fork relationship. Aftter you remove a fork relationship, you cannot send merge requests from your project to the source project. For more information, see [Unlink a fork](../repository/forking_workflow.md#unlink-a-fork). -- GitLab From 8aba6dff1e8bae653bd8dbc738f21d5f84d9107a Mon Sep 17 00:00:00 2001 From: Amy Qualls Date: Tue, 21 Nov 2023 21:20:53 +0000 Subject: [PATCH 12/15] Apply 3 suggestion(s) to 1 file(s) --- .../merge_requests/creating_merge_requests.md | 26 +++++++++++-------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 3abb96f2df398c..2bbe5fa4b63da5 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -16,14 +16,16 @@ To create a merge request, you must follow the branch name guide. For more infor You can create a merge request from the list of merge requests. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Merge requests**. -1. In the upper-left corner, select **New merge request**. -1. Complete the fields. +1. On the left sidebar, select **Merge requests**. +1. In the upper-right corner, select **New merge request**. +1. Select the source branch that contains your changes. +1. Select the target branch you want to merge your changes into. 1. Select **Compare branches and continue**. -1. Complete the fields. +1. On the **New merge request** page, complete the fields. 1. Select **Create merge request**. -Merge requests follow a one-to-one branch relationship. Each target branch can have only one open merge request at a time. +Merge requests follow a one-to-one branch relationship. Each target branch can have +only one open merge request at a time. ## From an issue @@ -37,12 +39,14 @@ Prerequisites: To create a merge request and branch from an issue: -1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Issues** and find your issue. -1. From the **Create merge request** dropdown list, select **Create merge request and branch**. You can use the default branch name, or create a different name. -1. Select **Create merge request**. -1. Complete the fields. -1. Select **Create merge request**. +1. At the bottom of the issue description, select the **Create merge request** + dropdown list. +1. In the dialog, make sure **Create merge request and branch** is selected. +1. If you don't want to use the default branch name, enter a different **Branch name**. +1. If you want to base your merge request on a tag, or a branch other than + the project's default branch, enter a **Source** branch. +1. Select **Create merge request** to open the merge request form. +1. Complete the fields in the **New merge request** form, then select **Create merge request**. When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). -- GitLab From b14e2b30c684286d6ad8b7b66476183aee6549f1 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 21 Nov 2023 17:10:13 -0800 Subject: [PATCH 13/15] Added back information --- .../merge_requests/creating_merge_requests.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 2bbe5fa4b63da5..04f62ae3fcbdd4 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -31,14 +31,12 @@ only one open merge request at a time. > Create merge requests redirects to the merge request creation form [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349566) in GitLab 14.8. -Create a merge request and a branch from an issue. When you create a merge request from an issue, the new branch and merge request are marked as related to the issue. The issue automatically closes when the merge request is complete unless automatic issue closing is off. For more information, see [Disable automatic issue closing](../issues/managing_issues.md#disable-automatic-issue-closing). - -Prerequisites: - -- You must have at least the Developer role for the project. +You can create a merge request and a branch, or only a branch, from an issue. When you create a merge request from an issue, the new branch and merge request are marked as related to the issue. The issue automatically closes when the merge request is complete unless automatic issue closing is off. For more information, see [Disable automatic issue closing](../issues/managing_issues.md#disable-automatic-issue-closing). To create a merge request and branch from an issue: +1. On the left sidebar, select **Search or go to** and find your project. +1. On the left sidebar, select **Issues** and find your issue. 1. At the bottom of the issue description, select the **Create merge request** dropdown list. 1. In the dialog, make sure **Create merge request and branch** is selected. @@ -48,6 +46,12 @@ To create a merge request and branch from an issue: 1. Select **Create merge request** to open the merge request form. 1. Complete the fields in the **New merge request** form, then select **Create merge request**. +After the branch is created, you can edit files in the repository to fix +the issue. When a merge request is created from the new branch, +the description field displays the [issue closing pattern](../issues/managing_issues.md#closing-issues-automatically) +`Closes #ID`, where `ID` is the ID of the issue. This closes the issue when the +merge request is merged. + When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). You can also begin your Git branch name with the issue number and a hyphen to link a merge request to an issue. For more information, see [Prefix branch names with issue numbers](../repository/branches/index.md#prefix-branch-names-with-issue-numbers). -- GitLab From c3106c5a95843b6c6f535dac9363df613c73fd91 Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 21 Nov 2023 17:24:26 -0800 Subject: [PATCH 14/15] Added a few small edits --- doc/user/project/merge_requests/creating_merge_requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index 04f62ae3fcbdd4..a455ce36943775 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -29,7 +29,7 @@ only one open merge request at a time. ## From an issue -> Create merge requests redirects to the merge request creation form [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349566) in GitLab 14.8. +> [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/349566) the Create merge request button to open the merge request creation form in GitLab 14.8. You can create a merge request and a branch, or only a branch, from an issue. When you create a merge request from an issue, the new branch and merge request are marked as related to the issue. The issue automatically closes when the merge request is complete unless automatic issue closing is off. For more information, see [Disable automatic issue closing](../issues/managing_issues.md#disable-automatic-issue-closing). -- GitLab From dd642ce579e250f9d6c11a065a5fc5dd9bc51d1b Mon Sep 17 00:00:00 2001 From: Alexandra Licht Date: Tue, 21 Nov 2023 22:47:07 +0000 Subject: [PATCH 15/15] Moved sentence for better organization --- doc/user/project/merge_requests/creating_merge_requests.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md index a455ce36943775..e19f31c1388951 100644 --- a/doc/user/project/merge_requests/creating_merge_requests.md +++ b/doc/user/project/merge_requests/creating_merge_requests.md @@ -52,9 +52,7 @@ the description field displays the [issue closing pattern](../issues/managing_is `Closes #ID`, where `ID` is the ID of the issue. This closes the issue when the merge request is merged. -When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). - -You can also begin your Git branch name with the issue number and a hyphen to link a merge request to an issue. For more information, see [Prefix branch names with issue numbers](../repository/branches/index.md#prefix-branch-names-with-issue-numbers). +When you create a branch from an issue, the issue ID is automatically included in the branch name. To change the default pattern, see [Configure default pattern for branch names from issues](../issues/managing_issues.md#closing-issues-automatically). You can also begin your Git branch name with the issue number and a hyphen to link a merge request to an issue. For more information, see [Prefix branch names with issue numbers](../repository/branches/index.md#prefix-branch-names-with-issue-numbers). ## When you add, edit, or upload a file -- GitLab