 Okay, hello. This is William and Sarah at GitLab. And today we're going to show you how to make a merge request to the handbook when your content is in a Google Doc. So it's always, always much better to make the merge request first right away and skip the Google Doc. And then you can skip this whole video. But in case you have content in the Google Doc that you want to get in a merge request, we're going to walk through how to set that up today. So the first thing we're going to do is go to the handbook page that we want to edit. And go to the bottom of the screen and click on edit this page. You might need to drag your browser window around. And then this will bring up the actual markdown page and go ahead and click on edit. Which is up in the toolbar area over there. And so this is a markdown representation of this page. And if you want to learn markdown, there's a video on our YouTube channel that talks about how to learn markdown in five minutes. Or at the bottom of this screen, there's usually a little link that says markdown. Actually it's not here. We'll link in the description video of this video a link to the markdown video. But if you Google GitLab markdown, you'll find how to learn markdown. So you're going to find the spot in this that you want to edit. And what I find is when I'm using this editor view, it says soft wrap up in the top right corner. And if you click on that, it kind of wraps the lines and makes it easier to read instead of going off the screen. So I think we want to edit the approval workflow. Is that right? Yes. So the first thing I think is that the point four about the invoice, we want to move that down into the preceding section or to the following section. Yes. Yeah. So go ahead and copy and paste that. I don't want the numbers though. So. Yeah. Cool. And then this whole section we're going to replace with the content in your Google doc. Is that right? Yes. So I would delete that stuff. Cool. And now we're going to go over to your Google doc. So go over to the Google doc that has your content. And command a to select all of the content. And then, you know, command C to copy it. And then in another tab, you are going to Google for rich text to markdown. And usually the first one that pops up is this Medusas. I use this all day long, one of my favorite tools and you just paste in your Google doc content there, convert to markdown. And you have a reasonable view there. So now you just copy all of that, go over to your MR and paste that into that section. Now there's a few things that we're going to need to massage that I will point out. So if you notice that go up to the top where the subheader was. So the first thing is that procedure to pay process is got two hash marks. That means it's like a level two header. And then underneath that is requirement identification and approval workflow which are at level four. And then yours is also at level four. So ideally you want yours to be a level below, but I thought you would have to change all of your stuff. Instead, you should be able to make approval workflow just a level three. Same with that one and the same with the ones below it. That just happened to work out in a lucky way on this page. The idea is you want all of your headings nested. So fours go under threes, go under twos, et cetera. So the only other thing to clean up is when you do a rich text to markdown conversion is sometimes there's extra white space. So you can kind of see like between paragraphs sometimes there's like two or three spaces when there should only be one. Do I change color? No, don't think so. That's just showing that you have an active line. Okay. I didn't change color though. Now the last thing we're going to do is we are going to look for any links in your content that are two pages on about.gitlab.com. So I don't know if you know off the top of your head, within your content, did you link to other gilab.com pages? It looks like there's one there. So we are going to turn that from what's called an absolute link, which includes the whole URL into a relative path link, which basically means just delete HTTPS colon slash about.gitlab.com. And so it's just going to start with slash handbook. That's because the handbook is also at about.gitlab.com. So it knows that that is the URL. So do you have any other absolute paths? So other links to other things or other websites are fine, but if it's a link to about.gitlab.com, you want to make that a relative path. For example, up there. It's already cool. So now we're going to add a commit message. So you are going to give this something descriptive. It should be short, but descriptive about the change that you are proposing. Where? Down in the commit message section here. Yeah. So instead of just update update of the page is usually not very helpful. But if you give something short and descriptive and then you can see that it is already going to create up. You need to review more stuff. No, I think I'm good. And then you can see the target branch is already created a new branch for you. And we're going to start a merge request with these changes. So when you commit those changes, which you should go do now, it's now creating a new branch for you and it's creating a merge request. So this is the merge request where this contents not live yet, but we're making a request to merge it. So here you can tag the people that you want to review. For example, you would put, you know, like at Chase and you might, you know, you might ask them specifically like what you want them to look at or. I started out as a professional. That's I like Chase a lot. So I would never want to mess up his page, right? Like, I think that's a good, I don't think I need Jamie to look at anything in particular, just want to know it's done. So, uh, so the other thing is, um, you probably want Chase to approve it before it gets merged. Okay. Is that I would just like add in there and say, like, you know, if you approve, can you comment with your approval or something like that? And then, do you know who will be the final person who will click the merge button, like who is responsible for merging this? Probably Paul. Okay. So you could, uh, you could assign in the assignee there, although you, you want people to review this before, before you assign to Paul, you can leave the assignee blank for now and basically go down and, uh, hit, uh, create merge request or submit merge request. And now you have your MR. And what it's going to do is these, uh, little icons over here are, this is the pipeline and so your pipeline is going to run. It's going to create something called a review app, which means it's going to spin up, uh, a whole version of the website that has your changes already in it. So if other people want to read and review what you did, they can just look at that page. And so when that's done, we'll add the review app, um, so that folks can review it. And if other folks want to review it in the meantime, they can go down here to the changes section. And click on changes potentially. And then, uh, you can see what is called a diff between the handbook. So that is how you take a content that you have in a Google doc and add it to a merge request. Thanks everyone for playing along at home.