For readers in a hurry

• Version control with Git: The magic "undo" button for your code that tracks every change, with the ability to revert to a previous version at any time.
• The web-based platforms GitHub and GitLab offer user-friendly interfaces for collaboration, code sharing and interaction with Git repositories.
• Similarities and differences: core functions such as version control, collaboration tools and issue tracking.
• The right choice: Consider the nature of your project (open source or private), team size and workflow requirements.

In the world of software development, Git, GitHub and GitLab have become indispensable tools. They not only act as a means of version control, but also as drivers for collaboration and increased efficiency in the work process. Shared code editing, simultaneous tracking of changes and project storage are crucial for developers as they allow them to seamlessly revert to previous versions when challenges arise. But what exactly is behind the terms Git, GitHub and GitLab? In this article, we would like to answer these key questions.

Version control with Git

Git is an open source tool and offers several developers the opportunity to work on a project. The history of changes made is saved in a repository. A repository is a storage location that manages and stores all files, data and information of a project in a version control system. You can think of Git as a digital filing cabinet for your code that keeps track of every change and allows you to revert to a previous version at any time. Git is like an "undo" button for your entire project history. 

Use case: A development team is working on a new function. In the process, an error is accidentally inserted. With Git, they can easily revert to an earlier version of the code base without losing all their progress. The tool also recognizes when two developers are working on the same code at the same time and offers conflict resolution assistance in this case.

GitHub vs. GitLab: Hosting your code

GitHub and GitLab are platforms based on the Git version control system and are mainly used for version control of software projects. Developers can use GitHub or GitLab to host their Git repositories and collaborate on software projects from anywhere. In this context, Git acts as the underlying version control technology.

Use case: A marketing team working on a new website design uses GitHub or GitLab to save the website code. This way, the changes made by different designers can be tracked and reverted to a previous version if needed. Collaboration is simplified by being able to assign tasks and review workflows from others via pull requests - all on the same platform.

Git, GitHub & GitLab - terms and their meaning

Similarities between GitHub and GitLab

• Underlying technology: Both platforms are based on Git for version control. Developers who are familiar with Git commands can therefore switch seamlessly between the two web-based platforms.
• Core functionalities: The two platforms offer the following features 

" Version control with branching and merging to manage different code versions.

" Collaboration tools such as pull requests for checking and integrating code.

" Problem tracking for the management of errors, tasks and function requests.

" Web-based interface with desktop and mobile app integrations for easy access.

Differences between the two platforms

Both GitLab and GitHub offer features for Git version control and collaboration, but are geared towards slightly different needs. The differences are explained below:

Focus of GitHub and GitLab

• As a web-based hosting platform for Git repositories, GitHub is known for its vibrant developer community and open source friendliness. It offers a user-friendly interface and a large marketplace for developer tools.
• GitLab also sees itself as a web-based hosting platform, but focuses on a more comprehensive DevOps approach. It offers functions such as "integrated" project management tools, CI/CD pipelines and wiki functions.

Focus of the platforms

• GitHub: Provides a robust core set of version control and collaboration features, but lacks some built-in project management tools.
• GitLab: Offers a wider range of functions, which can reduce the need for external integrations.

Pricing

• GitHub offers a free tier with limited private repositories. Paid plans offer more storage space and advanced features.
• GitLab: The free version includes an unlimited number of private repositories, but has restrictions on the number of employees, duration and CI/CD functions. Paid plans offer improved scalability and security.

GitHub or GibLab - selection criteria

Type of project

• Open source project or community building: GitHub's focus on the community makes it an ideal solution.
• Private codebase with a focus on DevOps: GitLab's comprehensive range of functions could be an advantage.

Team size and workflow

• Small teams with simple requirements: Both platforms offer free versions, which may be sufficient to start with.
• Larger teams with complex workflows can benefit from the project management and CI/CD functions offered by GitLab.

Neither platform is inherently "better". The optimal choice depends on the specific project requirements and the team's workflows.

About Business Automatica GmbH:

Business Automatica reduces process costs by automating manual activities, increases the quality of data exchange in complex system architectures and connects on-premise systems with modern cloud and SaaS architectures. Applied artificial intelligence in the company is an integral part of this. Business Automatica also offers automation solutions from the cloud that are geared towards cyber security.