We used open-source Git and later used GitLab, which is a flavor of Git. GitHub, GitLab, Bitbucket, and Azure Repos are all flavors of Git. The underlying version-control functionalities come from Git, but different vendors have their own flavors. I have experience in all four of these, which are Git.

We were using Azure DevOps previously, and we switched to GitHub primarily due to cost. The automated build platform is costly on the Azure DevOps side but significantly less expensive on the Azure side.

Previously, we used IBM but because of the clients' requirements, we decided to move to GitHub. 

We did not previously use a different solution.

I have used on-premises repositories but it was a long time ago.

We did not use any other solutions before GitHub.

Prior to using GitHub, we used Subversion, or SVN and CVS. We switched to GitHub because of the cloud enablement as well as the ease of use.

I previously worked with GitLab. They are pretty much the same. GitLab does have a very good user interface. That's the main difference.

We used to use BitBucket, but when Microsoft announced that private repositories would be free on GitHub, we switched.

I did not use other repositories previously. 

There were other solutions that we used previously.

Previously, we were using Bitbucket. We switched to GitHub because it is the number one source code management platform, and it has the cooperation of the open-source community. It provides for better collaboration. We all participate in the open-source community.

There are more users on GitHub, compared to Bitbucket.

I have not used another solution prior to GitHub.

We used Bitbucket for version control.

We used TortoiseSVN for a short while for version control for one project. It’s a good one also.

We previously used Bitbucket and Azure Repos. We switched to GitHub because of its ease of implementation and ease of onboarding new users, as well as its integration with third-party tooling.

We used to use GitLab (the free version I think), which had frequent deployment issues. So that's why we shifted to GitHub.

We used different solutions prior to GitHub, such as Perforce and Rational.

I have previously used ClearCase and Submersion but have used GitHub for the past eight years. ClearCase is a centralized system but has expensive licenses and running processes within the system took a long time. This is the reason we moved to Github.

Some of these tools are associated with our parent company. We consume them. I believe they were set up by our parent company's tools team.

Initially, when I first joined the company, they were using another solution, and recently we decided to move to GitHub. We are currently using it on a daily basis.

There are other solutions that we use for source control and they're going to be migrating to GitHub.

I have previously used Jira. When I was using Jira, I wasn't applying projects, so they were funding the project and using the Jira platform for managing their product. Currently in the project I'm on, we don't have a lot of funds for Jira, so we searched for the open source and found GitHub. We liked it because it was solving all of our queries. Whatever our needs were, we were able to accomplish them with GitHub.

Out of all the solutions in this category, I would recommend this solution to other companies.
I rate GitHub a nine out of ten.

I have previously used SVN but I prefer GitHub, it seems to be more powerful than SVN. We have a centralized website and a better user interface. 

I previously worked on GitLab but find GitHub has many more options and features, particularly in terms of project and SQL management. It was easy to migrate from GitLab to GitHub.

We are currently using GitClub for company projects, and do not have plans to switch at this time.

I was previously using Jira and Bitbucket but now I'm 100% in GitHub. I switched because of my team - they didn't work on Bitbucket. This is the reason I left Bitbucket even though GitHub is more costly.

I was looking for a management tool. Of course, Jira is the first try. When I looked at it for the cloud there were two options - GitHub and Bitbucket. But when comparing Jira's license to the licenses for Bitbucket or comparing the price between Bitbucket and GitHub, I found it's really cheaper for me to have Bitbucket. But because my team was most familiar with GitHub I decided I had to go with it.

The project management sector really needs some improvement for GitHub. I don't know if GitHub made sense for me as a project manager. But for what it was, it's a really good tool.