Welcome to the GitLab 101 Tool certification page! Here you will find our 101 course on how to use GitLab.
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. recruiting, 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.
This GitLab 101 training should be completed within 30 days of joining GitLab to help you be successful and impactful in your role while using GitLab as a tool.
To get started with the GitLab 101 Tool Certification you will need:
GitLab is a web-based DevOps lifecycle tool that provides a Git-repository manager providing wiki, issue-tracking and CI/CD pipeline features, using an open-source license.
Summarized: GitLab is a complete DevOps platform, delivered as a single application.
This will make more sense once you understand all of the terminology.
All of these terms will be used at GitLab, but the most common ones are:
Before taking the quiz, practice your knowledge on technical terminology with these flashcards.
To use the flashcards, click on the link above. You can review the flashcards in a variety of different ways. You can use them like normal (virtual) index card flashcards with the vocab word on the front and click on the index card to reveal the definition on the back. You can also use the other flashcard functions such as: List, Practice, or Matching.
To move on to the next Lesson, take and pass the GitLab 101: Technical Terminology Quiz.
As you learned in the technical terminology portion, a GitLab Issue is the fundamental medium for collaborating on ideas and planning work in GitLab. That means if you are working on a project or idea and want to collaborate with other team members, you can open an issue to do that.
To open a GitLab issue:
It's possible that an issue will be opened in an incorrect project. If that happens, it is easy to move it to the correct project.
To move a GitLab issue:
To comment on a GitLab issue:
Knowing how to search for a GitLab issue can be very helpful, especially if you had been looking at it but hadn't made a comment or been tagged in it. If you know some key words that were in the issue, you should be able to find it! Here's how:
This resource has helpful tips on searching for an Issue.
Tags or labels are used to help sort and search for GitLab Issues.
Each GitLab Project has an Issue Board. These can be set up similar to how a kanban board would look. You can add different lists to the Issue Board based on "labels" in the project.
To move on to the next Lesson, take and pass the GitLab 101: Issues Quiz.
As you learned in the technical terminology portion, a GitLab Merge Request (MR) is a request to merge one branch into another. We want to reiterate that this is a "request" meaning you aren't going to break GitLab with just submitting your MR.
To create a merge request:
You can search for a GitLab Merge Request in the same way as you search for a GitLab Issue outlined above. The only difference is to select the "Merge requests" button in the top right, rather than the Issues button.
Take and pass the GitLab 101: Merge Requests Quiz.
To become certified in GitLab 101, you will have to pass (with at least an 80%) all three Lessons including: Technical Terminology, GitLab Issues, and GitLab Merge Requests.
We are always trying to improve. Please let us know what you thought of this GitLab 101 course by filling out our feedback form.