What GitLab Is and Does

Think of a shared workshop for a team of writers. Everyone keeps drafts in one place, someone reads each draft before it is published, a checker tests the finished piece, and a noticeboard lists what still needs doing. GitLab is that workshop for people who write software.

GitLab is a DevOps platform, meaning one website that supports the whole journey of software from idea to running product. "DevOps" is a blend of development (writing the code) and operations (running it for real users). Let's look at four jobs it does.

First, it hosts Git repositories. Git is the tool that records every change to your files, and a repository is the project folder along with its full history. GitLab stores a shared copy online so teammates can all work from it.

Second, it manages code reviews. A person proposes a change, called a merge request, and teammates read it, comment, and approve it before it joins the main project.

Third, it runs CI/CD pipelines. CI/CD stands for continuous integration and continuous delivery: a pipeline is a set of automatic steps, such as running tests and packaging the software, that starts whenever code changes. It is like the checker in our workshop who tests every draft the moment it arrives.

Fourth, it tracks issues. An issue is a note describing a bug, a request, or a task, and teams discuss and assign these in one place.

A common mistake is thinking you need GitLab to use Git. You don't; Git works on your own computer without it. GitLab becomes useful when people collaborate, or when you want automatic testing and organized tracking. For a solo project, it can still help, but it is optional.

So GitLab gathers four jobs in one place: storing Git projects, reviewing changes, automating checks, and tracking work. Git does the history keeping, and GitLab surrounds it with the teamwork tools. That is the whole picture, and you're already holding it.