From 99f38d0f14e028343454093de39087062c3ea027 Mon Sep 17 00:00:00 2001 From: Lee Surprenant Date: Mon, 17 Jul 2017 21:44:30 +0000 Subject: [PATCH] After the Merge Request has been merged -> After the Merge Request has been created I assume this was typo. Offering a documentation merge request to test it :-) --- doc/user/project/merge_requests/cherry_pick_changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/project/merge_requests/cherry_pick_changes.md b/doc/user/project/merge_requests/cherry_pick_changes.md index 64b94d81024231..ee66d53b7c1e14 100644 --- a/doc/user/project/merge_requests/cherry_pick_changes.md +++ b/doc/user/project/merge_requests/cherry_pick_changes.md @@ -9,7 +9,7 @@ with introducing a **Cherry-pick** button in Merge Requests and commit details. ## Cherry-picking a Merge Request -After the Merge Request has been merged, a **Cherry-pick** button will be available +After the Merge Request has been created, a **Cherry-pick** button will be available to cherry-pick the changes introduced by that Merge Request: ![Cherry-pick Merge Request](img/cherry_pick_changes_mr.png) -- GitLab