GitLab / Handbook Help

Here's a quick way to find the reason your pipeline is failing using GitLab (and a great example of the importance of high-quality error messages).

Derek shares with Monica a high-level overview of what regular expressions are and why they are useful. This chat is geared for those less familiar with programming.

Learn more about searching GitLab like a pro: https://about.gitlab.com/handbook/tools-and-tips/searching/

You can search repositories in GitLab for changes using Git file History and Git blames.

https://docs.gitlab.com/ee/user/project/repository/git_history.html
https://docs.gitlab.com/ee/user/project/repository/git_blame.html

Git file History provides information about the commit history associated with a file, while a blame provides more information about every line in a file, including the last modified time, author, and commit hash.

In this video, Sarah Daily, marketing operations manager at GitLab, shows Wil Spillane, social marketing manager at GitLab, how to add a new page to your section of the handbook complete with a new main page and table of contents.

A short presentation and live demo to understanding why your pipeline fails.

Quick overview of how to go about identifying why a pipeline might be failing for a merge request to the handbook.