Hello everyone, if you do not know, we began to publish translations of the release articles of GuitLab.
If you missed the previous ones, here are the links: 8.10 , 8.9 , 8.8

GitLab releases releases on the 22nd of each month.
Translation of the post about the release of 8.11 in the work, but for now I submit to your court another article from the blog GitLab about the difference of terminology in GitLab, GitHub and Bitbucket.

Depending on the work tasks and customer needs, developers have to use different repository management platforms. A typical developer participates in some open source project on GitHub, and at work, the project is hosted by one client on GitLab, and another on Mercurial and Bitbucket. Switching between platforms is complicated by the fact that in them the same things can be called quite differently. In this article we will help you to compare the differences and at the same time explain why we chose such names.

Starting from version 8.4 in GitLab, the migration of repositories from GitHub has significantly improved. Now GitLab imports not only repositories, but also wiki pages, tickets and pull requests. However, most entities do not change their name. For example, Git specific terms such as commit or push are the same everywhere. General terms such as users, webhooks and issues do not change.

But some terms are still different. For example, the fact that in GitHub and Bitbucket is called a pull-request (pull-request), we call it a merge-request. We called it that because it is a request for a merge branch for the selected feature (feature branch) with a master branch; The actual pull command does not apply anywhere. By the way, Git has a separate request-pull command: it also allows you to suggest your changes and still uses the pull command, but it has a completely different mechanism .

If you are just starting to work with GitLab, this table will help you get started faster:

Teams, Repositories and Organizations

Let's see what is the difference between a team (team), repository (repository) and organization (organization). In GitHub, repositories contain the actual Git or SVN repository, as well as issues (tickets), participation statistics, etc. At the same time, users often call repositories projects.

In GitLab, we have eliminated ambiguity by explicitly calling such a structure a project . The project includes the Git repository, tickets, merge requisitions and everything else. On the project configuration page you can:

• Select the features used.
• Set project avatar.
• Set project visibility level: public, internal (for authorized users) or private (only for group members).
• Move, archive or delete a project.
• Configure the use of Gitlab CI in the project.
• Add services to integrate the project with third-party applications.

It is important to understand that even if you import into GitLab only a clean Git repository or something that is called a “repository” in the source, as a result you always get the GitLab project.

An important difference: in a Bitbucket project (project) is the union of several repositories. Such projects, in turn, belong to teams . In GitHub, organizations (organizations) perform a similar task.

In GitLab, such structures that combine several projects are called groups . Members of the group have access to read, modify and customize projects, depending on their role in the group. Each project belongs to only one group, but it can be “shared” for other groups. This feature is in Gitlab Enterprise Edition, as well as in GitLab Community Edition since version 8.5 . If you want to explicitly prohibit the sharing of projects, this can be done in the group settings.

Hope this article has helped you better understand the terminology. If you still have questions, ask them in the comments.

Translator: nick_volynkin