What is Git?

Git is a version control system used to track changes in computer files. Git's primary purpose is to manage any changes made in one or more projects over a given period of time. It helps coordinate work among members of a project team and tracks progress over time.

What is Gitlab?

GitLab is a web-based DevOps lifecycle tool that provides a Git-repository manager providing wiki, issue-tracking and continuous integration and deployment pipeline features, using an open-source license, developed by GitLab Inc.

How to work with GitLab?

In GitLab, you use groups to manage one or more related projects at the same time.

You can use groups to manage permissions for your projects. If someone has access to the group, they get access to all the projects in the group. You can also view all of the issues and merge requests for the projects in the group, and view analytics that show the group’s activity.

For larger organizations, you can also create subgroups.

More about groups, subgroups and members at https://docs.gitlab.com/ee/topics/set_up_organization.html and https://docs.gitlab.com/ee/user/project/code_owners.html .

To view groups:

1. On the top bar, select Menu > Groups.

2. Select Your Groups. All groups you are a member of are displayed.

Also the same actions to see your projects.

When you open the page of your group, you can see projects (repositories) of this group or subgroup.

More about projects at https://docs.gitlab.com/ee/user/project/working_with_projects.html and at https://docs.gitlab.com/ee/user/project/repository/ .

For example, here is a repository «project» in subgroup «group0».

It is your repository to publish project tasks.

There is a branch switching control in the upper-left area of the project’s webpage. Each branch can be treated as an isolated state of the project sources intended for a particular development goal.

A branch is a version of a project’s working tree. You create a branch for each set of related changes you make. This keeps each set of changes separate from each other, allowing changes to be made in parallel, without affecting each other.

For example, “master” branch typically contains production-ready state of the sources corresponding the accomplished version of the product. “develop” branch typically contains shared work-in-progress state of the sources. Other branches can be created to isolate parts of work on the project while being in process before they’ll be ready to merge into “develop” branch to be shared with other participants of the project.