We use GitHub for code repository alongside Bitbucket.

View full review »

My primary use case involves working with GitHub for code management. I have extensive experience using it for various tasks, such as creating repositories, managing pull requests, and utilizing GitHub Actions for automating workflows.

View full review »

I am entrenched in DevOps tools and have been working with GitHub primarily for enterprise administration, structure, and access. I came from a very large company and now work with a mid-size to larger company, where I help administer and keep the platform running smoothly for our development teams. View full review »

I use GitHub for our development codebase. It's our single source of truth where we push all our application code.

View full review »

We use GitHub as a code repository for version control. We store our automation code there and have our own branching strategy. It supports our Continuous Integration and Continuous Deployment (CI/CD) processes by allowing us to implement CI/CD tools effectively.

View full review »

Mainly, I implement my automation test or automation scripts on GitHub, and I try to set it up and push it. Whenever the dev team pushes or makes any deployment, I look for it in GitHub to verify everything is there. Then, I test those features that they deployed.

View full review »

I always use GitHub for version control, DevOps, GitHub Action, and Jenkins connection. GitHub is a very reliable version-controlling system. In the last year, I have been using GitHub for my cloud project, using the config server and keeping some security code there. I have not used it for artificial intelligence projects.

View full review »

I use AutomationEdge, and we also work with solutions from Microsoft Azure and AWS. We are using Azure OpenAI and AutomationEdge for AI solutions. For unstructured data, we are working on doing POCs, and we have completed POCs with true AI and AutomationEdge combination. We are trying to implement agentic solutions and agentic RPAs using true AI and AutomationEdge.

View full review »

I use GitHub just for remote repositories, backup, and version control. I also use local Git.

View full review »

I mostly use GitHub to save repositories that I encounter when scrolling or searching for resources. Even if they are not immediately relevant to me, I know they will be useful in the future. So, I save those repositories in my GitHub account. Whenever there is any requirement from a client or a project with a similar base, I use those repositories for the data.

View full review »

I use GitHub for version controlling of the code. I have experience using GitHub to upload the source code and manage tasks.

View full review »

I use GitHub and the products from its integration partners, which include SOAR platforms, ServiceNow integrations, IBM integrations, Splunk integrations, and much more.

I use the solution in my company for code management and platform management purposes.

View full review »

I mainly use it as a repository for source code. I worked on a project where the tool was also used for the CI/CD pipeline, but I didn't set up the pipelines, so for the whole test case, I just participated in the project.

View full review »

GitHub is used to maintain code in a centralized place, which allows multiple teams to work on the same repository. It is also integrated with Jira and other tools like CACD pipelines. GitHub streamlines project collaboration by enabling developers to clone, modify, and push changes into a centralized repo. It supports project collaboration for software development processes.

View full review »

We have more than 100 teams in our organization using GitHub because it is a centralized repository tool. We have many interdependent applications, and GitHub provides a platform where people can share their codes in a particular directory.

View full review »

For GitHub, we host our app there, and the code is secured up there in GitHub. We have multiple projects built there. The code is in the GitHub cloud, and we use it as a storage bucket for our codebase that stores our multiple projects and repositories. We use GitHub Actions to automate workflows; whenever we add a new feature to the project or app, GitHub Actions automates testing, deployment, and checks best code practices.

View full review »

The tool helps in collaboration with our team on version control, and we're very happy with it. 

View full review »

We use GitHub for developers' deployments and issue management. We follow a Scrum setup, utilizing boards, story-testing tasks, and epics for effective visualization.

View full review »

I use it for repositories. We use it for version control and for deployments. We use pipelines in GitHub to deploy projects in Salesforce.

View full review »

We use GitHub to track what kind of libraries you are using.

View full review »

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.

View full review »

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. 

View full review »

I use GitHub as a code repository, and we use GitHub Actions a lot to trigger our pipelines.

View full review »

The solution is used by developers to work as a team on a code. 

View full review »

The solution is used to store code. It is a repository manager for our code. We can also configure it to run our deployment.

View full review »

I use GitHub to keep and maintain my code and have version control. I connect with GitHub through an application called GitHub Desktop.

View full review »

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

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

View full review »

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. 

View full review »

I use GitHub for development, including version control and container services.

View full review »

View full review »

GitHub is an excellent platform for organizing all sorts of information. I personally found it beneficial for keeping track of my coding projects, and recommendations, and occasionally making commits. By creating branches, I could easily focus on specific areas and even delve into things like creating my website using GitHub pages. Overall, I found these features to be very practical and advantageous.

View full review »

We use GitHub for source control.

View full review »

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.

View full review »

We primarily use the solution for sourcing candidates.

View full review »

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.

View full review »

GitHub is essentially a repository of code. It's where you source your code with the client and allows you to use Git. You get versioning and everything else for multiple deployments or codes. That's how we use it.

View full review »

We just use GitHub for the repository in our company.

View full review »

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. 

View full review »

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

View full review »

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

View full review »

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

View full review »

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. 

View full review »

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.

View full review »

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

View full review »

Our organization uses GitHub for version control.

View full review »

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

View full review »

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

View full review »

We primarily use the solution for version control.

View full review »

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.

View full review »

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

View full review »

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.

View full review »

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.

View full review »

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

View full review »

We are customers of GitHub.

View full review »

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

View full review »

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

View full review »

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. 

View full review »

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.

View full review »

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

View full review »

The primary use case of this solution is for version control and source code management.

View full review »

We used the product for CI/CD.

View full review »

I'm mostly using the solution for the backup repository. We are also using it for bug tracking and Scrum management.

View full review »

I use the solution as a repository to store the source codes that I create with small tools. I also use it to share codes with customers when it is impossible to directly upload them from my computer to the customer’s environment due to some network restrictions. However, it is possible to download from GitHub in such environments. So, I transfer my source codes through GitHub so that they can download and implement them.

View full review »

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

View full review »

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.

View full review »

We use this solution for DevOps activities.

View full review »

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.

View full review »

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

View full review »

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

View full review »

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.

View full review »

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.

View full review »

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. 

View full review »

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

View full review »

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.

View full review »

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. 

View full review »

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.

View full review »

We use GitHub for versioning and to provide a place on the cloud to store code so that people can work on it together.

View full review »

Some of the people in my team use this solution for version control of personal projects.

View full review »

We use GitHub for AI features.

View full review »

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

View full review »

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.

View full review »

I use GitHub for work and personal projects.

View full review »

GitHub is mainly used for code control. We have three environments, and we keep their codes as per those environments. As and when required, we clear pull requests as well. The main purpose of GitHub is to keep our code available.

View full review »

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.

View full review »

We use GitHub as a repository. 

View full review »