Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 36 ยท Getting Started

What Is GitLab?

Learn what GitLab is, how it differs from plain Git, what GitLab.com, Self-Managed and Dedicated mean, and how an idea travels from issue to production.

Git is a tool that records the history of your files. GitLab is a web platform built around Git: it hosts your repositories and adds everything a team needs around the code, such as issue tracking, code review, automated builds, a package registry, security scanning and deployment. One application, one login, one place to look.

This lesson explains the big picture: what GitLab is made of, the ways you can run it, and how a single change moves from an idea to a running service. The rest of the course zooms into each stage, with special attention to GitLab CI/CD.

About the examples. GitLab is a hosted product with a server, so it cannot run inside this website. When a lesson describes menus or commands, we describe them precisely but never invent output. The runnable <TryIt> blocks are small stand-ins written in Python: they model one idea (parsing a URL, evaluating a rule, ordering jobs) so you can experiment. They are not GitLab itself, and every one is labelled as a stand-in.

Git versus GitLab

Git works on your computer. You commit, branch and merge locally, and you can share work through any server that speaks the Git protocol. GitLab is one such server, plus a large web application on top of it.

Git (the tool) GitLab (the platform)
Stores commits, branches and tags Hosts repositories and shows them in a browser
Merges branches on your machine Merge requests: discussion, review, approvals, automated checks
No notion of tasks Issues, boards, milestones, epics
Cannot build or deploy CI/CD pipelines that run on machines called runners
Nothing to store artifacts Package, container and Terraform registries

If you are not yet comfortable with branches and remotes, read the Git tutorial first. This course assumes you can commit, push and pull.

One platform for the whole lifecycle

GitLab describes its scope as the DevSecOps lifecycle: plan, create, verify, secure, package, release and monitor. Each stage maps to features you will meet in this course.

From idea to production

Plan Issues and boards
Create Branches and merge requests
Verify CI pipelines and tests

Everything starts as an issue and ends as a deployment.

1 / 2

Because these features share one data model, they link to each other. A commit message can close an issue, a merge request shows its pipeline result, and a pipeline can deploy to an environment that appears on the project page. In a toolchain made of separate products you would wire all of that together yourself.

The ways to use GitLab

There are three common ways to get a GitLab instance.

  1. GitLab.com is the hosted service run by GitLab itself. You sign up and start. It includes hosted runners, so pipelines work immediately. Most people and small teams start here.
  2. GitLab Self-Managed means you install GitLab on your own servers or cloud account (Linux packages, a container image, Helm for Kubernetes). You control upgrades, data location and network access, and you are responsible for running it.
  3. GitLab Dedicated is a single-tenant instance that GitLab operates for you, for organizations with strict isolation requirements.

Features also vary by tier: Free, Premium and Ultimate. Free covers repositories, issues, merge requests and CI/CD. Premium adds things like required approvals and merge trains. Ultimate adds the full security and compliance suite. Throughout the course we say when a feature needs a paid tier, and you should always confirm in the current documentation because tier boundaries change over time.

There is also a free, open-source core (Community Edition) and a source-available Enterprise Edition. The paid tiers unlock Enterprise Edition features with a license.

Anatomy of a GitLab address

Every project lives at a predictable address: a host, a path of groups, and a project name. Understanding it makes cloning and navigation easier. The stand-in below splits a clone URL into its parts and builds the SSH form.

Python Stand-in: take a GitLab project URL apart

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice that groups can hold more than one name. GitLab lets you nest groups into subgroups, which is how large companies mirror their organization chart. The next lessons cover this in depth.

A first tour of the journey

Here is the path a typical change takes, using only features you will learn in this course.

flowchart LR
  A["Issue #42"] --> B["Branch 42-fix-login"]
  B --> C["Commits and push"]
  C --> D["Merge request !7"]
  D --> E["Pipeline runs on a runner"]
  E --> F["Review and approval"]
  F --> G["Merge to main"]
  G --> H["Deploy to production"]

The numbers #42 and !7 are GitLab references: # is an issue, ! is a merge request.

You write the code in your own editor and use Git as always. GitLab supplies the shared state: the issue that explains why, the merge request that discusses how, the pipeline that proves it works and the environment that shows where it runs.

Here is a second stand-in that prints this journey as a checklist, with the kind of artifact each step leaves behind. Change the steps to describe your own team's process.

Python Stand-in: your change's paper trail

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common misunderstandings

  • GitLab is not Git. Deleting a project on GitLab does not delete the clones on your machine, and Git works fine without any server.
  • GitLab is not only CI. Pipelines are the most famous part, but you can use GitLab purely for repositories and issues.
  • "Free" does not mean "unlimited". GitLab.com has quotas (for example, compute minutes for hosted runners and storage limits). Self-managed instances have the limits you configure.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the best description of GitLab?

    Git is the version-control tool; GitLab is the platform built around it, with collaboration, automation and delivery features.
  2. 2. You want full control over where the data is stored and when upgrades happen. Which option fits?

    Self-Managed means you run GitLab on your own infrastructure. GitLab.com and Dedicated are operated by GitLab.
  3. 3. In the address https://gitlab.com/acme/web/shop, what is the project name?

    The last path segment is the project; the segments before it (acme/web) are the group and subgroup.
  4. 4. Which reference points to a merge request?

    is for issues and ! is for merge requests.

Summary

  • Git is the local version-control tool; GitLab is the platform that adds collaboration, CI/CD, registries and security.
  • You can use GitLab.com, run Self-Managed, or have GitLab operate a Dedicated instance.
  • Features depend on the tier: Free, Premium or Ultimate.
  • A project address is host plus group path plus project name.
  • A change flows through issue, branch, merge request, pipeline, review, merge and deployment.

Next: Your Account and Finding Your Way Around