GitLab MR-Buddies, 26 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Create Handbook Page and WIP MR

Description

This video is part of our GitLab 201 course.

A

Okay, so we are going to walk through how you uh create a new page and we're also going to create new page using a work in process merge request. So what you first need to do is go to the www.getlab.com project, so we are there and then to find where to put this page, we're going to make a gitlab 201 page. So this is where the get lab 101 page is.

A

You can see it's in the handbook, people, group learning and development certifications, gitlab 101, so what we will do is go to sites handbook, source handbook and then we're looking for so now we're in uh this part of the url. So we're gonna look for people group next, so it's in alphabetical order.

A

Here's people group, the next part- is learning and development.

A

Here's that folder.

A

And then certifications.

A

It's here and then this page is get lab 101. We want to create another page here, so our new url would be the same as this except here, except it would be gitlab 201, it's not a page yet so it won't pull anything up, but we want to create a new page in this folder.

A

So in here I will click this little plus area or arrow, and then new file.

A

And then what I do, because I I'm not good at remembering how to create a page. I just pull up one, that's similar to what I want to create and open it.

A

So I did view source and then now I'll click edit and see how this is set up.

A

So I should be able to I'll just copy this. To name it gitlab 201, slash make sure it has index.html.md. That makes sure the page is formatted in the correct way um and since you're already in like the certifications, folder, you don't have to type you don't have to type. Let's see if I can get to go, you don't have to type this because you're already there. So it's like handbook, slash people group, slash, learning and development, certifications you're already in that folder. So you just need to type this part.

A

So whatever you're going to name the page, slash index.html.md, so we did that and then the next step is to make sure the format of the page is set up correctly. So I normally just go copy a little bit of a different page, and then I go to the page. I'm creating- and I paste it in here so this will be 201.

A

A

Updates before we submit this so the title of the page, let's see.

A

So what is right here is what will populate here on this banner.

A

So that's what the title does and then all this just make sure the page is set up and format formatted the same as our other handbook pages.

A

So we will go down here to the commit message and get new.

A

Started target branch will be get lab, 201 page.

A

And then we will go ahead and commit the.

A

A

And it's going to take forever to load because we're recording okay cool. So um this will be the title of the merger. Merge requests so I'll. Just.

A

Page and then just add some details in here: oh and we're going to create, make this a work in process so that um you can continue to add on it until we decide it's ready to merge so work in process create new gitlab 201 page, and that also makes it so it can't be merged. So the working process you'd have to go in and actually remove that before it can be merged.

A

A

A

And then I'm going to assign this to kiki, so you get a notification. I can also add myself to it. If I want so, I'm going to go ahead and submit the merge request.

A

And here is the merge request for this, so you can go in and make more changes to it. So you just go to the changes. Tab, click, this little pencil button and add more details. So maybe you want to add.

A

Prerequisites, I don't know if that's spelled right, but that's okay, because we can go in and make more changes. um So okay, lab 101 would be a prerequisite to this and then I'll just add, update the commit message to just a brief summary of what I did so add. Prereq.

A

Section you'll leave the target branch, the same, commit changes and then it will be added to.

A

The merge request that we just created.

A

And yes, it will take a long time because we're recording.

A

Okay, cool, so I might have to refresh it you'll be able to see yeah. There are two commits you could go into each of these and see what was changed for each, um but this changes tab will show you like all the changes. So if we were to remove something, there would be a red.

A

Like highlight to show you that something was removed, so this is a work in process. Merge, request, say: you've made all your changes and you want to merge it or you want to assign it to someone to merge it. You can see that you can't merge this one, because it is a work in process, so what you would do to be able to merge, it would be go in here. Remove the whip, part, save the changes and then just make sure you assign it to whoever is going to review and merge it.

A

So you can see this will change. It could be added to the merge train when the pipeline succeeds, I'm going to go ahead and add the whip back, because we want it to be a work in process, but just so you can see what you need to do to merge it, but that is how you create a new handbook page and also do a merge request.