GitHub Reviews

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.

Any complex banking can be handled very easily in GitHub. It allows us to integrate with tools like Grid, where we can merge and resolve conflicts without any hassle. 

This solution could be improved if migration was fully automated to make it easy, for example, to migrate repositories into GitHub. 

I have used this solution for eight years. 

The customer service for this solution is not great. The team either takes a long time to respond or doesn't respond at all. 

Neutral

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.

The initial setup is straightforward and only involved four to five steps. 

I would rate this solution a ten out of ten. 

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.

All the features are valuable, but the most important feature is that GitHub has advanced security. The second important feature is the capability to create custom GitHub actions and the capability to deploy in different types of architectural infrastructures, such as hybrid, private, or public.

It is not technical. It is more about how people perceive GitHub in terms of the security of the code. They need to understand that if they have a repo on GitHub, it is not public for everyone.

They're improving the work items to track the progress of the team, but in my experience, Azure DevOps is better in this functionality. GitHub needs to improve the form to track the progress of the work done by a team.

I have been using it for more or less one year.

It is, for sure, stable.

It is definitely scalable.

They were very helpful.

I have experience in many tools. GitHub is not the hardest, and it is also not the easiest. It is of medium level.

I would advise trying out the Advanced Security model, which is its best functionality.

I would rate it a 10 out of 10.

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.

It is easily accessible. Even if someone doesn't have the paid version of the GitHub license, the minimum license, they can still use it for themselves. Sometimes Jira extensions are only installed on a server on the client side, so you need a VPN connection to access that, but with GitHub access is based on your ID, so you can access it from anywhere.

While we are working from home because of the pandemic—and when we didn't have proper VPNs—it helped us assess all our defects, which are placed in GitHub very easily. We don't need to rush the VPN connection and then access all these things. It was really easy. It also has two-factor authentication, which helps us authenticate users very easily.

A great feature is being able to have different repositories and different kinds of projects in a single solution at a single time. It's just a click away. If I compare it with Jira, that's one of the best features.

The only thing I see missing in GitHub is that it isn't very user friendly for key personnel who don't have in-depth, technical knowledge. In Jira, there are many functions to upload our test cases, and in GitHub we can only do it manually. There are functions which can be used to upload different files, but that still requires some technical knowledge. A layman cannot do it. Someone has to be trained with all those artifacts.

In the next release, I would like to see more QA friendly features like extensions. In Jira, you can modify different extensions. GitHub doesn't have that. They have many standard features, but sometimes I feel that there is something that I need but it's missing.

I've been using GitHub for more than three years.

GitHub is very stable. I have seen many different sections which are also easily accessible. For developing a product, you don't need to travel or do research work. In GitHub, there are many other repositories that are public. You can also navigate and see what others are doing if they have some public examples. It's like a type of overflow. You get many examples from this, and then by seeing those examples, you can directly implement that work and have a glimpse at other things.

Scaling the solution is very easy. 

In my organization, there are 130 people currently using GitHub. It has been used quite extensively because 130 guys are using it on a daily basis for checking their codes along with user stories.

We haven't needed anyone for maintenance of this solution.

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.

Initial setup was very simple.

There was no implementation strategy because GitHub is cloud based. It doesn't require any sort of deployment from our end. There was just a configuration that we needed to do to make it work with our code. There were simple sections which we needed to run, but our developers were able to collaborate easily.

We worked with our in-house team. There was no mediator between us.

If there are only 10 people using a particular repository, then GitHub is free. But if we increase the number of users, we need to pay the normal charge for GitHub.

I would rate this solution 7 out of 10. 

If someone is managing the product as well as doing the test management, they should go with GitHub. It's very easy to understand and track everything, and you can even see the different check-ins. 

If someone is specifically going for a test management tool and they need the proper agile-based tools, they should go for Jira.

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

The solution is open-source and is built around a whole community. 

The product offers an easy way of supporting our or approaching our repository and updating our code.

The solution has been stable for us. 

It can scale well. 

The product has been secure enough. We haven't had any issues with security.

I cannot recall coming across any shortcomings of the product. 

I've been using the solution for three years. 

We haven't had any issues with stability. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. For how we use it, it's reliable.

It is a scalable solution. 

We are not a private company. We are a part of a government institution and we are the IT office of that government institution. There are 14 of us using GitHub.

The product does have a good community around it that can assist users. 

We've never reached out to GitHub technical support services. 

There's no installation process. 

The solution is open-source and free to use. 

I would recommend the solution to other users and organizations. We have been quite satisfied with its capabilities. 

I'd rate it eight out of ten. 

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

The product has a good UI. It's simple and easy to access, and technical help is easily available. The two-factor authentication security is another valuable feature. 

I would like a more graphical, user-friendly UI, to avoid writing so much code on cmd.

For personal use, I've been using the solution for two or three years. But in my office, we started using it this year.

Stability is good, it's stable. I haven't found any issues to date, even though it's big data. It works well.

It's a scalable solution. 

We have an infrastructure team that handles technical support and everything else. The things we need are easily available on the internet.

Positive

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

My organization installed everything, including the two-factor authentication security. 

We implemented the solution in-house.

I would rate the solution nine out of ten.

We use this solution for DevOps activities.

The flexibility of this solution has been most valuable. It operates on a pay per use basis where you can ramp up or decrease usage.

This solution could be improved by offering crowd sourced support where we could ask questions to other users. 

I have been using this solution for three years.

This is a stable solution. 

This is a scalable solution. We haven't had any problems where we've run out of capacity. We have 50 users on this solution. 

This solution does not require a big installation. It can be used as and when it is needed without a huge commitment.

I would recommend using Githib to others. 

I would rate this solution a nine out of ten. 

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

While using the solution when merging two code branches the code becomes a bit messy. This should be improved in the future.

I have been using this solution for approximately six years.

The solution has been completely stable.

The scalability is good. We had 20 developers using the solution and now we have 200, there have not been any problems.

The technical support was very good.

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

The initial setup was straightforward.

The price of this solution is reasonable.

Out of all the solutions in this category, I would recommend this solution to other companies.

I rate GitHub a nine out of ten.

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

This solution is very easy to use which I like about it. The capacity to own artifacts and share them with others is another good feature. You don't have to write all your code from scratch, you can use available templates and alter the code according to your needs.

The initial setup and implementation could be easier, I had some difficulties with it at first but I don't have a development background.

I've been using this solution for around one year. 

The solution is pretty stable and straightforward, but having experience helps.

I found this product to be scalable, we have at least 500 to 600 users within our company. For a small-scale deployment two people are more than sufficient, but that would increase with the complexity of the deployment.

Any issues have been resolved by our own team, but I can say that Microsoft customer support is usually satisfactory.

The initial deployment was straightforward and took three to four months.

I would rate this solution an eight out of ten.