Our customer has hundreds and thousands of applications, and 12 are part of my current project. Three of those applications are using GitHub as a code repository. The rest use Bitbucket. This customer is an Atlassian shop, so only I don't think more than 50 people use it.

Any code they develop will be version-controlled in this GitHub tool, and they use the branching and merging strategy to promote their code. We use it for version control and parallel development.  

The code in GitHub will be consumed by CI/CD pipeline for the build and deployment. We're using the latest version, which has a feature called GitHub Actions that enables CI/CD within GitHub, but this organization doesn't use GitHub Actions. They prefer Bamboo. 

We use GitHub because we don't have any paid solutions, and GitHub is freeware. It's open to all, and there aren't big licensing fees, like with Jira or any other tool. Apart from that, because it's totally cloud based, we don't need any extensions, and our developers and DevOps are all in sync and are able to get help with their second branches. So, we are all using the same platform to manage our product.

It's a cloud solution.

Currently, the solution is our source control system. We manage the DevOps pipeline for the company and it's the version control backbone.

My primary use case for GitHub is for my private projects that I'm developing for my customers. Some customers have their own developers and I sometimes support them to achieve their goals. So we share everything. We're also using GitHub for the documentation for the teams. I also give lectures for the organizations because sometimes they have development teams but they are not qualified enough, so I have to give them some training on it.

We use the solution when developing new code or modifying existing code, changes are tracked and other team members can review the code before production. 

We use the solution to handle our switch control. All our first code force is managed by GitHub to commit new features and create different branches. We even use this to manage the code to handle flows and processes. We can use it to create some branches and manage the code ownership, and we have an account for each developer so that they can submit pieces to code review for the user. 

We primarily use the solution for version control.

We use this product to host the code base for different development teams within our organization and for versioning the codes and integrating with CI/CD tooling. We have a partnership with GitHub and I'm a product manager. 

Our primary use is for open-source code management and distributed version control. We use the solution to coordinate the work of developers, assisting them in developing and maintaining our source code. We also use the tool for code review purposes using the GitHub repository, where I can comment on or review lines of code for developers to edit and improve performance. They then receive a notification alerting them of the desired update, which the project developer and project lead can approve.

We are actually working with MuleSoft, and for that, we have to build our application. We are working for a company offering hotels and resorts. We are using GitHub for that process. We're building applications on it. 

It's mostly for versioning only, maintaining code branches, and sharing the code across to the wider community. It depends if it's a private one or a public one. It's mostly for collaboration across people.

Our primary use case of this solution is for collaboration, code sharing, and as a testing environment. We can put it into Docker and create images. I'm the technical lead in the company and we are customers of GitHub. 

We use GitHub for code versioning; with multiple developers working on the same projects. It gives us a central source for our code. We commit our code to the cloud using the API called Gita, which tracks which developers have uploaded the code, which have changed it and so on. 

We use GitHub to share the source code and can give users different permissions to use different parts of the project. Whenever a developer changes a source code, it can push it easily, and others can see the change and who made it.

Basically, it's just a repository for software developers. Users are able to push their source code and share their code.

We are using GitHub for the development environment. After we develop some applications, we are pushing actually on both settings. 

We are an IT service company that specializes in DevOps, and we use many tools for application lifecycle management, such as GitHub, GitLab, SonarCloud, SonarQube, Docker, Kubernetes, and Azure DevOps. 

We mainly use this solution for storing the code of our applications and our scripts. We also use it for our automated functional testing and for building applications and releasing applications. It is also used to manage our team and our product, as well as to check the security of our product. 

We are a partner and reseller, and we use GitHub Cloud.

We are mainly using it for product development. Our repo and code are in GitHub.

It is a cloud-based solution. It is a part of our subscription in the cloud, and we have its latest version.

We are using GitHub as a repository for a couple of customers to be able to do Infra as Code in Microsoft Azure for them.

We use Github to upload projects and share files. Github is used for personal application development and building plugins, Normally, we manipulate GitHub from the native system, so we upload the files to GitHub and get a URL. My company has more than 300 developers, and about half of them use GitHub for application storage and formatting applications.

I am a senior product development engineer and I use GitHub in this capacity.

Essentially, this is the Git product, but in the cloud.

We use GitHub for the resource management of our central system. We are customers of GitHub and I'm a solution architect.

It's a code repository, so it is used for checking it, code, and version control.

This solution is deployed on the cloud. 

There are 10-15 people using this solution in my organization.

We use GitHub for the development process of our online applications.

The solution mainly serves as our project repository. We use it to maintain different environments with the help of branches.

GitHub is used to manage distributed versions of systems to allow developers using production operating systems to work without distributed dependency. It is a distributed version control system where we get the repository downloaded on our laptops and can work without any idle time.

We use this solution for completing repository services code on Azure. We use it for different customers and to design and test environments. We also use it for some background testing.

We primarily use the solution for sourcing candidates.

We use GitHub whenever there is an infrastructure level deployment on any of the cloud platforms.

Our organization uses GitHub for version control.

Our primary use case is as a software repository. I've also used it for projects with several developers and a team leader who worked on the source code and put it into the master repository. From there they started the existing CI/CD pipeline which deployed the microservices into the OpenStack. I'm an architect and design the solution, integrating it with the components. We are customers of GitHub.

I use Github to store the code that I write. I don't use it very much. It may be used more by the active developers.

Syed:
So, basically, I can store my code in some repository, so we can manage also that version control. So, if he developed some applications, so we can manage with versions, so that feature GitHub provide, so we can create some repositories. Through repositories, we can manage the versions, so it's very useful. So, also and that GitHub provide some CI/CD pipeline feature, so we can integrate CI/CD through GitHub, so whenever I commit that code, it will automatically deployed in our servers, so it was a very useful feature in GitHub.

We are using GitHub for all of our repositories. We can store the code, collaborate with different developers, build, and create a pipeline.

We are customers of GitHub.

We used it mainly for version control and when we wanted to test an application at the initial stage or launch the mock-up version.

GitHub is specifically designed for repositories and it works perfectly for storing code. We use it for our source code repository.

We use this solution when we speak about the storage, sizing requirements, and POCs.

We use GitHub to manage repositories, pull requests from partners and merge new changes. 

We use this solution for DevOps activities.

I use the solution to store most of my Python projects.

We use this solution to manage and store our development work.

We use GitHub for source control.

We use this solution to exchange files and manage version control.

We use it to collaborate on projects, and store projects as well. 

GitHub is used to store my source code or raw reports.