Need advice about which tool to choose?Ask the StackShare community!

Git

293.8K
175.8K
+ 1
6.6K
GitLab

61.1K
52.4K
+ 1
2.5K
Add tool

Git vs GitLab: What are the differences?

Git and GitLab are both version control systems that are used for managing and tracking changes in code repositories. However, there are some key differences between the two.

  1. Hosted vs Self-hosted: Git is a distributed version control system that can be used locally or on remote servers. On the other hand, GitLab is a web-based Git repository manager that can be self-hosted or accessed through a hosted service.

  2. Collaboration Features: Git provides basic collaboration features such as branching, merging, and pull requests. GitLab, on the other hand, offers enhanced collaboration features like issue tracking, code review, and continuous integration/continuous deployment (CI/CD) pipelines.

  3. Access Control: Git has limited access control mechanisms and relies on the file system permissions for controlling access to repositories. GitLab, on the other hand, provides fine-grained access control with user roles, permissions, and group management.

  4. Web UI: Git has a command-line interface (CLI) for performing actions, while GitLab provides a web-based user interface (UI) that makes it easier to navigate and interact with repositories.

  5. Integration: Git can be integrated with various external tools and services using custom scripts and hooks. GitLab, on the other hand, has built-in integrations with popular development tools and services, making it easier to automate workflows.

  6. Community and Support: Git has a large and active community with extensive documentation and support resources available. GitLab also has a growing community and offers commercial support for enterprise customers.

In summary, Git is a distributed version control system with basic collaboration features, while GitLab is a web-based Git repository manager that provides enhanced collaboration features, access control, a web UI, integrations, and commercial support options.

Decisions about Git and GitLab
Weverton Timoteo

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

  • Pick the correct target branch
  • Make Drafts explicit
  • Name things properly
  • Ask help for tools
  • Remove the noise
  • Fetch necessary data
  • Understand Mergeability
  • Pass the message
  • Add screenshots
  • Be found in the future
  • Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

See more
Weverton Timoteo

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

See more
Weverton Timoteo

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

See more
Kamaleshwar BN
Senior Software Engineer at Pulley · | 8 upvotes · 678.6K views

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

See more

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

See more
Nazar Atamaniuk
Shared insights
on
DeployPlaceDeployPlaceGitHubGitHubGitLabGitLab

At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Git
Pros of GitLab
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 959
    Fast
  • 845
    Open source
  • 726
    Better than svn
  • 368
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Role-based codelines
  • 11
    Disposable Experimentation
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Github integration
  • 3
    Easy branching and merging
  • 2
    Compatible
  • 2
    Flexible
  • 2
    Possible to lose history and commits
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Light
  • 1
    Team Integration
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Easy
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    It's what you do
  • 0
    Phinx
  • 508
    Self hosted
  • 431
    Free
  • 339
    Has community edition
  • 242
    Easy setup
  • 240
    Familiar interface
  • 137
    Includes many features, including ci
  • 113
    Nice UI
  • 84
    Good integration with gitlabci
  • 57
    Simple setup
  • 35
    Has an official mobile app
  • 34
    Free private repository
  • 31
    Continuous Integration
  • 23
    Open source, great ui (like github)
  • 18
    Slack Integration
  • 15
    Full CI flow
  • 11
    Free and unlimited private git repos
  • 10
    All in one (Git, CI, Agile..)
  • 10
    User, group, and project access management is simple
  • 8
    Intuitive UI
  • 8
    Built-in CI
  • 6
    Full DevOps suite with Git
  • 6
    Both public and private Repositories
  • 5
    Integrated Docker Registry
  • 5
    So easy to use
  • 5
    CI
  • 5
    Build/pipeline definition alongside code
  • 5
    It's powerful source code management tool
  • 4
    Dockerized
  • 4
    It's fully integrated
  • 4
    On-premises
  • 4
    Security and Stable
  • 4
    Unlimited free repos & collaborators
  • 4
    Not Microsoft Owned
  • 4
    Excellent
  • 4
    Issue system
  • 4
    Mattermost Chat client
  • 3
    Great for team collaboration
  • 3
    Free private repos
  • 3
    Because is the best remote host for git repositories
  • 3
    Built-in Docker Registry
  • 3
    Opensource
  • 3
    Low maintenance cost due omnibus-deployment
  • 3
    I like the its runners and executors feature
  • 2
    Beautiful
  • 2
    Groups of groups
  • 2
    Multilingual interface
  • 2
    Powerful software planning and maintaining tools
  • 2
    Review Apps feature
  • 2
    Kubernetes integration with GitLab CI
  • 2
    One-click install through DigitalOcean
  • 2
    Powerful Continuous Integration System
  • 2
    It includes everything I need, all packaged with docker
  • 2
    The dashboard with deployed environments
  • 2
    HipChat intergration
  • 2
    Many private repo
  • 2
    Kubernetes Integration
  • 2
    Published IP list for whitelisting (gl-infra#434)
  • 2
    Wounderful
  • 2
    Native CI
  • 1
    Supports Radius/Ldap & Browser Code Edits

Sign up to add or upvote prosMake informed product decisions

Cons of Git
Cons of GitLab
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 7
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    When --force is disabled, cannot rebase
  • 2
    Ironically even die-hard supporters screw up badly
  • 1
    Doesn't scale for big data
  • 28
    Slow ui performance
  • 9
    Introduce breaking bugs every release
  • 6
    Insecure (no published IP list for whitelisting)
  • 2
    Built-in Docker Registry
  • 1
    Review Apps feature

Sign up to add or upvote consMake informed product decisions

What is Git?

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

What is GitLab?

GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Git?
What companies use GitLab?
See which teams inside your own company are using Git or GitLab.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Git?
What tools integrate with GitLab?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Mar 24 2021 at 12:57PM

Pinterest

GitJenkinsKafka+7
3
2166
GitJenkinsGroovy+4
4
2704
GitCloudBees+2
3
4471
Git.NETCloudBees+3
6
1077
Mar 4 2020 at 5:14PM

Atlassian

GitBitbucketWindows+4
3
1092
GitNode.jsFirebase+5
7
2378
What are some alternatives to Git and GitLab?
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
SVN (Subversion)
Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
Bitbucket
Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
Perforce
Visibility, access control, workflow and code management for Git environments. Flexibility of collaborating on the same codebase and code reviews using any combination of Perforce and Git workflows and tools without compromise.
Mercurial
Mercurial is dedicated to speed and efficiency with a sane user interface. It is written in Python. Mercurial's implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds.
See all alternatives