summaryrefslogtreecommitdiff
path: root/doc/topics/git
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2022-11-23 12:11:34 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2022-11-23 12:11:34 +0000
commit2c29837ce1692790dedccbc9b36b44dc8aaacbee (patch)
tree779a007b58f6f7ec95f0058291309d20637f918d /doc/topics/git
parentabbb493d78e42f044d732c7ad46917300cca1516 (diff)
downloadgitlab-ce-2c29837ce1692790dedccbc9b36b44dc8aaacbee.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/topics/git')
-rw-r--r--doc/topics/git/feature_branch_development.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/topics/git/feature_branch_development.md b/doc/topics/git/feature_branch_development.md
index de9f9980811..d53c8eae835 100644
--- a/doc/topics/git/feature_branch_development.md
+++ b/doc/topics/git/feature_branch_development.md
@@ -77,7 +77,7 @@ In this case, the feature branch would be `release-X-Y`. Assuming the `release-X
1. After you select **Create merge request**, an option to **Change branches** displays. Select that option.
-1. In the **New Merge Request** screen, you can now select the **Source** and **Target** branches.
+1. In the **New merge request** screen, you can now select the **Source** and **Target** branches.
In the screenshot shown,
we have selected `test-branch` as the source, and `release-13-0` as the target.
@@ -87,14 +87,14 @@ we have selected `test-branch` as the source, and `release-13-0` as the target.
You should see an entry similar to:
```plaintext
- New Merge Request
+ New merge request
From test-branch into release-13-0
```
An entry like this confirms your merge request's destination.
-1. Make any additional changes in the **New Merge Request** screen, and select **Submit merge request**.
+1. Make any additional changes in the **New merge request** screen, and select **Create merge request**.
1. In the new merge request, look for **Request to merge**. An entry similar to this displays:
```plaintext