Need advice about which tool to choose?Ask the StackShare community!
Git vs GitLab: What are the differences?
Git: Fast, scalable, distributed revision control system. 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; GitLab: Open source self-hosted Git management software. 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.
Git can be classified as a tool in the "Version Control System" category, while GitLab is grouped under "Code Collaboration & Version Control".
"Distributed version control system", "Efficient branching and merging" and "Fast" are the key factors why developers consider Git; whereas "Self hosted", "Free" and "Has community edition" are the primary reasons why GitLab is favored.
Git and GitLab are both open source tools. Git with 27.9K GitHub stars and 16.1K forks on GitHub appears to be more popular than GitLab with 20.1K GitHub stars and 5.33K GitHub forks.
Netflix, Asana, and CircleCI are some of the popular companies that use Git, whereas GitLab is used by Ticketmaster, Citrix, and Electronic Arts. Git has a broader approval, being mentioned in 3891 company stacks & 4632 developers stacks; compared to GitLab, which is listed in 1219 company stacks and 1431 developer stacks.
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?
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?
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.
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.
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!
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.
Pros of Git
- Distributed version control system1.4K
- Efficient branching and merging1.1K
- Fast960
- Open source845
- Better than svn726
- Great command-line application368
- Simple306
- Free291
- Easy to use232
- Does not require server222
- Distributed27
- Small & Fast22
- Feature based workflow18
- Staging Area15
- Most wide-spread VSC13
- Role-based codelines11
- Disposable Experimentation11
- Frictionless Context Switching7
- Data Assurance6
- Efficient5
- Just awesome4
- Github integration3
- Easy branching and merging3
- Compatible2
- Flexible2
- Possible to lose history and commits2
- Rebase supported natively; reflog; access to plumbing1
- Light1
- Team Integration1
- Fast, scalable, distributed revision control system1
- Easy1
- Flexible, easy, Safe, and fast1
- CLI is great, but the GUI tools are awesome1
- It's what you do1
- Phinx0
Pros of GitLab
- Self hosted505
- Free428
- Has community edition338
- Easy setup241
- Familiar interface239
- Includes many features, including ci136
- Nice UI112
- Good integration with gitlabci83
- Simple setup56
- Has an official mobile app34
- Free private repository33
- Continuous Integration30
- Open source, great ui (like github)21
- Slack Integration17
- Full CI flow13
- Free and unlimited private git repos11
- User, group, and project access management is simple9
- Intuitive UI8
- All in one (Git, CI, Agile..)8
- Built-in CI7
- Full DevOps suite with Git5
- Both public and private Repositories5
- CI5
- Build/pipeline definition alongside code4
- Integrated Docker Registry4
- Mattermost Chat client4
- Issue system4
- It's powerful source code management tool4
- So easy to use4
- Excellent4
- Dockerized3
- Low maintenance cost due omnibus-deployment3
- On-premises3
- Security and Stable3
- I like the its runners and executors feature3
- It's fully integrated3
- Unlimited free repos & collaborators3
- Great for team collaboration3
- Free private repos3
- Because is the best remote host for git repositories3
- One-click install through DigitalOcean2
- Review Apps feature2
- Built-in Docker Registry2
- Powerful software planning and maintaining tools2
- Multilingual interface2
- Groups of groups2
- Beautiful2
- Wounderful2
- Opensource2
- Not Microsoft Owned2
- Published IP list for whitelisting (gl-infra#434)2
- Kubernetes Integration2
- Many private repo2
- HipChat intergration2
- The dashboard with deployed environments2
- Native CI2
- It includes everything I need, all packaged with docker2
- Kubernetes integration with GitLab CI2
- Powerful Continuous Integration System2
- Supports Radius/Ldap & Browser Code Edits1
Sign up to add or upvote prosMake informed product decisions
Cons of Git
- Hard to learn16
- Inconsistent command line interface11
- Easy to lose uncommitted work9
- Worst documentation ever possibly made7
- Awful merge handling5
- Unexistent preventive security flows3
- Rebase hell3
- When --force is disabled, cannot rebase2
- Ironically even die-hard supporters screw up badly2
Cons of GitLab
- Slow ui performance28
- Introduce breaking bugs every release8
- Insecure (no published IP list for whitelisting)6
- Built-in Docker Registry2
- Review Apps feature1