Need advice about which tool to choose?Ask the StackShare community!
GitHub vs GitLab: What are the differences?
Developers describe GitHub as "Powerful collaboration, review, and code management for open source and private development projects". 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. On the other hand, GitLab is detailed as "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.
GitHub and GitLab can be categorized as "Code Collaboration & Version Control" tools.
Some of the features offered by GitHub are:
- Command Instructions
- Source Browser
- Git Powered Wikis
On the other hand, GitLab provides the following key features:
- Manage git repositories with fine grained access controls that keep your code secure
- Perform code reviews and enhance collaboration with merge requests
- Each project can also have an issue tracker and a wiki
"Open source friendly", "Easy source control" and "Nice UI" are the key factors why developers consider GitHub; whereas "Self hosted", "Free" and "Has community edition" are the primary reasons why GitLab is favored.
GitLab is an open source tool with 20.1K GitHub stars and 5.33K GitHub forks. Here's a link to GitLab's open source repository on GitHub.
reddit, Instacart, and Lyft are some of the popular companies that use GitHub, whereas GitLab is used by Coderus, Webedia, and Ticketmaster. GitHub has a broader approval, being mentioned in 4647 company stacks & 5874 developers stacks; compared to GitLab, which is listed in 1219 company stacks and 1431 developer stacks.
Yours thankfully, Darkhiem
Hey there, Definitely install Git. Git is the open source version control system that both GitHub and GitLab interface with. Git is extremely important as a new developer to learn, and once you do, you will be so thankful you are tracking your projects in it. Git makes it super easy to track changes you make in your code, and even rollback, edit, view, or delete changes you made months before. In software development, it is a crucial skill to learn.
GitHub and GitLab are online cloud Git repositories. They are for backing up your repos in the cloud, and working with other developers, or even working with yourself via other devices. I would recommend starting with GitHub since you are a new developer. Companies will want to see your GitHub when you start applying to jobs, and having one will be a great plus going for you. It also is the most widely used by developers and most open source projects are hosted on GitHub.
Here is a course on Codecademy to start learning: https://www.codecademy.com/learn/learn-git
Hope this helps! Good luck!
I think Github is the most important thing, so take good care of it, and share your most important programs on it with others, this helps to raise your efficiency through the feedback of others. with my Greetings.
Hey! Regardless of your choice of platform, you will need to install and learn Git. So start there! The differences between GitHub and GitLab are not relevant to you at this stage.
For python, Pycharm is a very nice and beginner friendly IDE. I am using it myself, use the free community edition, it also comes with a lot of great tools.
I use GitHub by few years. For now, I think this is the best way to work on another computers or to work with other people. I tested GitLab and Git, but for me GitHub is easier and most friendly for another developers who are worked with me.
I would like some information regarding the benefits an aspiring start-up company may have, while using GitHub Enterprise vs the regular GitHub package. On a separate issue, I'd like to understand whether GitLab may have some DevOps-related advantages GitHub does not.
Thank you in advance, Matt
I'd lean towards GitHub (either billing plan) for one key reason that is often overlooked (we certainly did!).
If you're planning on creating OSS repositories under your start-up's name/brand, people will naturally expect to find the public repositories on GitHub. Not on GitLab, or Bitbucket, or a self-hosted Gitea, but on GitHub.
Personally, I find it simpler to have all of the repositories (public and private) under one organisation and on one platform, so for this reason, I think that GitHub is the best choice.
On the DevOps side, GitLab is far superior to GitHub (from my experience using both GitHub Enterprise and GitLab Ultimate), but for the one aforementioned, we're using GitHub at Moducate.
Advantages for Github Enterprise is that you get more storage, CI minutes, advanced security features, and premium support. If you don't really need any of those, you can stick with Github Team. Though if you're going to use Gitlab CI, I suggest going with Gitlab instead of Github so you won't have to maintain 2 repositories.
Regarding the advantages that Gitlab CI has over Github, there's a detailed explanation here: https://about.gitlab.com/devops-tools/github-vs-gitlab/ci-missing-github-capabilities/
If you need more minutes for Gitlab CI, you can always use your own Gitlab CI runners instead of the shared runners: https://docs.gitlab.com/runner/register/
With the advent of Gitlab actions/workflows, it's hard to not choose Github anymore. I say that with all love for Gitlab, as it's been my personal tool of choice for a long time because of it's inbuilt CI/CD solutions. Github is just all around more adopted by the community so you'll always find more support; and if you go with enterprise you will get 50k build minutes a month as well as a ton of extra tools that will definitely help a startup out from the get-go. That being said, it's priced at $21 per user, per month so if you cannot afford that, I say go with Github.
GitHub Enterprise comes with included SAML SSO support, and a huge free tier for Actions and Packages, which gives your team everything they need to get off to a great start and scale up without hitting any roadblocks along the way. An important point to consider is that GitHub Enterprise comes in both self-hosted and cloud-hosted variations, so you don't need to manage your own infrastructure for it unless you would prefer to.
With GitHub Enterprise, you also plug in to the largest development community in the world, and can collaborate directly on the open source projects that are probably already part of your stack. You can also access the latest and greatest in development tools such as GitHub Codespaces, GitHub Co-Pilot, and much much more, with great new features being shipped every day.
GitHub is trying to catch up with GitLab. GitLab was built from the ground up with DevOps tooling. GitHub is years away on features.
Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.
Now I want advice on below.
- Is it a good idea to migrate from Bitbucket to AWS Codecommit?
- If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
Hi Kavita. It would be useful to explain in a bit more detail the integration to Jira you would like to achieve. Some of the Jira plugins will work with any git repository, regardless if its github/bitbucket/gitlab.
I use GitHub as my primary code hosting, collaboration and CI/CD platform, as well as for my portfolio.
The reasons against GitHub:
- No fine-grained Permissions possible. Write-only for whole repo only. The fuck?. Not only will this potentially end in a disaster, it already ended up causing the necessity for every big multi-maintainer project to have an maybe-even-own-written GitHub App that allows specified users to do a specified set of things by posting comments that are structured as commands.
- GitHub Packages Size Limit
- [Addendum 2022/07] GitHub Actions is great in general, but it lacks some features in the long run / when you want to get more advanced. (e.g. early-exiting the job, getting the job or workflow id in a job, job-level if's for matrix'ed jobs). But!: You are not locked-in to use GitHub CI. GitHub integrates and shows the results of other CI systems too!
The reasons for GitHub are rather simple and more pronounced:
- Everyone, even non-Developers, know how to use GitHub.
- Everyone has an Account on GitHub.
- GitHub Actions are great and completely FREE (I repeat: free, unlimited access to great automated virtual machines that can do anything on any action trigger).
- GitHub Action runners are actual virtual machines (even windows/macos possible) and not just some hacky docker containers, allowing you to really do anything.
- The API and Documentation is top notch.
We chose github + github actions in order to manage the code versioning and the CI on the same software. Furthermore, while it is not that much, I believe that for a large team it is considerably cheaper to have one github subscription instead of a git subscription and a CI/CD software subscription.
GitHub provides great user experience ans most developers are familiar with it. There is also an attractive pricing model for those who already have a Visual Studio subscription.
We also don't like the "everything in one tool" approach from GitHub as there are better tools for build system, package registries, etc. on the market.
We chose GitHub for version control hosting because of its high-quality and performant pull request user interface, as well as GitHub Actions.
We also selected GitHub as our first OAuth2 authorization provider because of its large community, high-quality documentation, and sophisticated App framework for granular permission management and event notifications.
The company needed to move from hosting all of our repositories, tickets & releases from a GForge instance hosted by our former parent company. The decision was made to move to GitHub Enterprise but the developers were not told until there was 1 month left to go. So needed something that could pull all of our information out and push it to the new hosts and it needed to be done ASAP.
Do you have a K8s cluster and you want to deploy some services to it? Gitlab Auto Devops is key to achieve this without breaking a sweat.
We deploy Go services to our K8S clusters with warp speed thanks to Gitlab and it's Auto Devops pipeline.
I haven't seen tooling like this in any other git cloud provider.
Both of us are far more familiar with GitHub than Gitlab, and so for our first big project together decided to go with what we know here instead of figuring out something new (there are so many new things we need to figure out, might as well reduce the number of optionally new things, lol). We aren't currently taking advantage of GitHub Actions or very many other built-in features (besides Dependabot) but luckily it integrates very well with the other services we're using.
I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.
I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.
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?