Welcome to GitLab 201. This is a self-paced course consisting of reading material, video tutorials and knowledge assessments at the end of each lesson. To become complete GitLab 201, participants will have to pass all 3 lessons with at least 80%. We recommend that courses are completed and passed in order.
Please visit GitLab Learn and create an account to complete the GitLab 201 and earn the GitLab 201 Badge!
Everyone at GitLab needs to know how to use GitLab and be technical to some level. This training is geared toward GitLab team members who are in non-engineering roles (i.e. talent acquisition, peopleops, marketing, finance, etc) and/or have not used a DevOps tool like GitLab before. This can also be helpful for non-engineering people outside of GitLab wanting to learn how to use GitLab for personal projects.
To get started with the GitLab 201, you will need:
A laptop
Wifi
2 hours (this course can be completed in one sitting or lesson by lesson)
Epics let you manage your portfolio of projects more efficiently and with less effort by tracking groups of issues that share a theme, across projects and milestones. Epics are great for project management as they help to better enhance your workflow.
Epics are created on group level. To create an epic, navigate to the project’s group, on the left panel,
You may choose to mark confidential by selecting Make this epic confidential checkbox.
A child epic is a sub epic created within the parent epic. You may think about it like a folder with sub folders and multiple files. Child epics may be added to a parent epic.
To add a child epic:
An epic contains a list of issues and an issue can be associated with at most one epic. When you add an issue that’s already linked to an epic, the issue is automatically unlinked from its current parent.
In the epic, click the Add dropdown button.
For an existing issue, navigate to the side bar,
click epic, type in the title of the epic you want to add and then select it from the drop down menu.
Once the desired epic has been selected, it will be shown on the issue like this:
Issues - medium for collaborating on ideas and planning work in GitLab
Boards - set up similar to how a kanban board would look. An issue board shows you what issues your team is working on, who is assigned to each, and where in the workflow those issues are.
Epic - helps to track issues across multiple projects efficiently. Epics give a high level view of the health status of different issues attached to that epic.
Please complete the Lesson 1 assessment in Level Up
In GitLab 101, we learned how to create merge requests. In this lesson, we will dive deeper into merge requests.
You can review a merge request to provide feedback to the author. You can start a review in the merge request diff. Diff is the view of changes to a file between branches or commits.
To review a merge request: Click on the "Changes" tab in the merge request.
Click on the line you want to comment on, using the 'add a comment icon'
Write your comment in the dialogue box and click on the start a review button.
To add more comments to a review, start writing a comment as normal and click the ‘Add to review’ button.
To resolve a thread, when replying to a comment, click the checkbox to resolve thread.
Click "submit review" to publish all documents.
You can suggest changes in the merge request diff threads. The Merge Request author is able to apply these suggestions with a click, which will generate a commit in the merge request.
Choose a line to be changed, click add a comment icon
Then click on the Insert suggestion icon in the toolbar
In the comment, add your suggestion to the pre-populated code block
Click "Start a review" to add your comment to a review, or "Add comment now" to add the comment immediately.
The suggestion in the comment can be applied by the merge request author directly from the merge request.
Once the suggestion has been applied, a new commit will be created and the suggested change will be pushed to the merge request's branch.
If you are still working on a merge request and not ready for it to be merged, add WIP: or Draft: to the start of the merge request’s title, this will prevent the merge request from being merged.
To update a WIP MR, in the changes tab, click on the pencil icon to edit the merge request.
Make your changes. Click "commit changes".
When you are ready for it to be merged, simply remove the WIP: or Draft: prefix from the title of the MR.
Save changes, and assign the merge request to the DRI of the page.
Please complete the Lesson 2 assessment in Level Up
Before creating a new handbook page, ensure the information does not already exist in the handbook or if it can be added to an existing page.
Navigate to www-gitlab-com project
Click on sites - handbook - source - handbook
Navigate to the specific folder that will house the new page
In that folder, click the + icon and select new file
Name the file path and ensure it ends in /index.html.md.
To ensure the page is set up correctly, copy/paste the following to the top of your new handbook page. Remember to edit appropriately.
---
layout: handbook-page-toc
title: "[insert title of your page]"
description: "[insert a short sentence to appear as part of search results]"
---
## On this page
{:.no_toc .hidden-md .hidden-lg}
- TOC
{:toc .hidden-md .hidden-lg}
Type in the commit message and click commit changes.
Update the merge request template and assign the merge request to the appropriate revieweer.
To locate the handbook on gitlab.com, navigate to www-gitlab-com project, click sites - handbook - source - handbook. Click the section of the handbook you want to navigate to (eg people group, marketing), the folders are arranged alphabetically.
The markdown guide page contains useful tips for updating the handbook, such as adding images, embedding documents and much more.
If you don’t know how to do something - find another instance of it in the handbook. For example, if you want to add a table to the handbook. Navigate to a section of the handbook that contains a table, the People Group page is a good example. Click view source to see how the table looks. You may copy/paste, then edit to suit your needs.
Please complete the Lesson 3 assessment in Level Up
To complete GitLab 201, you will have to pass (with at least an 80%) all three lessons.
We are always trying to improve. Please let us know what you thought of this GitLab 201 course by filling out our feedback form in Level Up.