We haven't used any other similar solution before GitLab.

I have used GitHub before. GitHub now comes with an AI Assistant, similar to a copilot, its most significant advantage. With this copilot, it assists you in writing code. It provides examples and helps you rectify errors, especially during migration processes. Additionally, it offers previews of how migration can be performed. These enhancements are attributed to Microsoft’s support and involvement in OpenAI.

Earlier, we were using Atlassian products, and then we shifted to GitLab.

I used GitHub. GitHub did not have a container registry or testing, and it is owned by Microsoft, which raises concerns about ethics. All my decisions are based on ethics. 

I have experience using GitHub, but GitLab is a superior platform. One major advantage of GitLab is the ability to maintain a private cloud with a wide range of features. It also allows for quick setup of CI/CD pipelines. Garrett is becoming popular amongst developers for code maintenance.

I have used Bitbucket and GitHub for personal use. We adopted GitLab because it's a good enterprise solution.

Our organization decided to use GitLab because it's easy to use, and its user interface is more intuitive than other tools.

Our company currently uses UrbanCode for deployments. Eventually, we want to conduct all deployments in the solution. 

We previously used IBM CLM and RTC.

I'm also familiar with Bitbucket, although I don't use it right now. 

I have previously used Bitbucket and Filezilla.

I tried to learn a little bit about Jenkins, however, it was only through some internet content.

We are familiar with GitHub. 

We were using Subversion. GitLab is a little bit more complex than Subversion, but it is okay for me.

We previously used Jenkins. Jenkins management is more complicated than GitLab. GitLab is easier to manage. Because of the simplicity of the product, GitLab is better than Jenkins.

We haven't used any other build automation product other than GitLab.

I previously used Gerrit and I prefer GitLab. It is much better in the interface and integration, it is much more than only Git software, it is more of a complete package.

I have previously used GitHub as a developer. GitLab looks similar to GitHub and it's helping the developer use it better.

We did previously use a different solution. I can't recall the name.

We changed Bitbucket for GitLab.

Previously, we used Jenkins and GitLab without the pipeline and the Runner.

I also use GitHub and I am more comfortable with GitLab.

I have used a variety of tools, including Ansible, Terraform, Bitbucket, and Bamboo.

We have used many solutions before GitLab.

I have previously used Bit Bucket and Github. Bit Bucket has some issues in our country. At the time we had banning issues within our government and only GitLab was. Bit Bucket is too slow and we had to wait for five minutes just to enter the platform. 

Bit Bucket pipelines are not that easy to consider and it was harder to use than GitLab. Gitlab is also more customizable. GitHub is more expensive than GitLab and didn't offer CICD. 

It is subjective. I cannot compare GitLab with Azure because it is based on experience.

We also use GitHub. Earlier GitLab was more favored, but now GitHub has everything that is there in GitLab. If GitHub is offering more, then there might be chances of switching to that. I am not attached to either of these solutions. If things are working better for me in GitHub, I will move to GitHub.

We have tried out a lot of other products, including Azure DevOps. We have tried a lot of open-source products as well. The major benefit we found in this solution is it's a single platform doing everything. If I go to Azure DevOps, Microsoft would also say it's a single platform, yet it's not a single platform. They have integrated themselves with multiple toolchain vendors, and it's a Microsoft wrapper on the top. When it comes to Microsoft is a resource-hungry solution. You require a lot of resources to run on Microsoft.

I have used several tools like Ansible for deployment and Nexus as a repository. We moved to GitLab because these features are integrated into one solution

Previously, I used Team Foundation Server (TFS).

We used to use TFS repositories on the older versions of Microsoft.

We previously used SVN. We migrated everything over to GitLab.

We previously used BitBucket, but we have transferred everything to GitLab. Everything that BitBucket can do is available in GitLab.

I have used previously CVS. Both CVS and GitLab have their advantages and disadvantages. GitLab is in the cloud and can be accessed anywhere which is very flexible. For the functionality, I am not certain about the differences. I find them both to be good solutions.

Previously we used Team Foundation Server, but GitLab is better for local cloud deployment.

We compared this solution with Atlassian. Atlassian has Bitbucket and we felt GitLab is a little easier to use.

Prior to using GitLab, I was using GitHub.

Sometimes, clients migrate from Gitlab to Bitbucket. Sometimes, they migrate from Bitbucket to Gitlab. The most important feature that they are looking for is more integration with other tools, and they find Bitbucket a better solution for that.