Version control with GitLab

General

‘GitLab’ at the Projektablage is a suitable tool for collaboration in development projects, like for instance in software development.
In order to work with GitLab, you need to activate this IT-service first for your project space by ticking the box to the left of 'Git' in the project administration. By doing so, a namespace is created (named like your project space) in which Git repositories can be created (i.e. projects in the sense of GitLab). This namespace is visible to you when you log in to GitLab.

Note: In the following,  ‘project’ denotes a GitLab project - not your project space at the Projektablage!

Users and Roles

When handling the resources of a project, there are three distinct roles for the users, which are equipped with different permissions:

• Master: Is authorised to create projects in GitLab and to change the members's roles in them.
• Developer
• Reporter

Additional roles can be selected inside the application.

You can find an ample description of these roles and their permissions on this page.

Note: It is not possible to add or remove users in GitLab. This can only be done with the administration page of the Projektablage.

Note: The administrators of the project space automatically become GitLab users when Git is selected and they are assigned the 'Master' role.

Working with GitLab

The manufacturer of GitLab offers a comprehensive documentation.

Note: The role 'Developer' in GitLab corresponds to the RW permission in the former Gitolite - but with one difference: By default a 'Developer' is not allowed to write to the ‘Master’ branch. This becomes possible, when the master branch is set to ‘unprotect’.