From 941440099ca3dfe279f4e166d5cd9a33a404d820 Mon Sep 17 00:00:00 2001 From: Dara Warde Date: Thu, 25 Jul 2019 15:23:42 +0000 Subject: Adding use case for GL Team Member & link buddies --- doc/user/project/merge_requests/index.md | 6 ++++++ 1 file changed, 6 insertions(+) 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**. -- cgit v1.2.3