summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDara Warde <dara@gitlab.com>2019-07-25 15:23:42 +0000
committerDara Warde <dara@gitlab.com>2019-07-25 15:23:42 +0000
commit941440099ca3dfe279f4e166d5cd9a33a404d820 (patch)
treefb4d90c7246b05d1effba28b1be979a968c02b76
parentaa9db9c869ecbc570bd03f02dd3febf32f99d560 (diff)
downloadgitlab-ce-darawarde-master-patch-71639.tar.gz
Adding use case for GL Team Member & link buddiesdarawarde-master-patch-71639
-rw-r--r--doc/user/project/merge_requests/index.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/user/project/merge_requests/index.md b/doc/user/project/merge_requests/index.md
index d5ca853eff5..e15d4ff4b8f 100644
--- a/doc/user/project/merge_requests/index.md
+++ b/doc/user/project/merge_requests/index.md
@@ -73,6 +73,12 @@ B. Consider you're a web developer writing a webpage for your company's website:
1. Once approved, your merge request is [squashed and merged](squash_and_merge.md), and [deployed to staging with GitLab Pages](https://about.gitlab.com/2016/08/26/ci-deployment-and-environments/)
1. Your production team [cherry picks](#cherry-pick-changes) the merge commit into production
+C. Consider you are a GitLab Team Member
+
+1. You are wanting to edit the GitLab handbook
+1. See steps above
+1. You are not overly technical and are stuck on how to do the MR? Learn about our internal [Merge Request Buddies] (/handbook/general-onboarding/mr-buddies/).
+
## Merge requests per project
View all the merge requests within a project by navigating to **Project > Merge Requests**.