GitHub Reviews

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

GitHub storage is one of the main requirements and it could improve.

I have been using GitHub for approximately four years.

I have found GitHub stable.

GitHub is scalable.

Every developer in the R&D department is using GitHub in my company. There are approximately 2,300 people in the R&D department.

I have not contacted technical support to need to contact support.

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

The licensing model for GitHub is user-based. Whenever the new developer joins we have to get a new license and register their ID. The overall price of the solution is reasonable.

I would recommend the solution to others. It is very good.

I rate GitHub a nine out of ten.

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 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. 

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

The principal benefit of using this solution is being able to organize improvements and changes to code. This is particularly useful for projects which involve many people.

The control version functionality for this solution has been most valuable, especially when managing projects with multiple versions. 

The descriptions within Github could be more user-friendly to show the trees of Gitflow.

I have used this solution for ten years. 

This is a scalable solution. 

We have not needed to contact customer service. All the information we have needed has been available on the web. 

The initial setup is straightforward.

I would rate this solution a ten out of ten. 

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.

GitHub is simple to use and has great performance. Even if I'm not in the office, I can access and work on my code from anywhere with my account credentials. GitHub has an interactive user interface.

The solution should have less integration with the AI part, but it needs to add features with other automation tools so that it can be easily integrated.

I have been using GitHub for five and a half years.

Around 200 users are using GitHub in our organization.

The solution’s initial setup is straightforward.

If I go as per the process we follow, it will take hardly half an hour for me to deploy the solution.

You don't have to pay for a license if you are using the free version. It gives you all the possible features it has.

GitHub is deployed on the cloud in our organization. Users who have to manage their code can create a GitHub account and start using it.

Overall, I rate GitHub ten out of ten.

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.

There was versioning software before. It's now on the cloud and it's kind of available from anywhere, et cetera. You can access it from anywhere, and if you want, you can collaborate with a wider audience if you make a public repository. Otherwise, whatever was existing in versioning software, probably that's taken to the web and to the cloud to scale. 

The differences that they give upfront are good. You can evaluate and check whatever is being shared.

It's stable.

The solution can scale. 

We find it user-friendly.

Mostly they have the features that we need and they are currently being used. There are two approvals already. However, if something has to be moved into approvals, and if they don't approve it in a few hours, then they should move the approval request to some other user, or they should have a way to escalate it.

I've used the solution for only a year now. 

The solution is stable. There are no bugs or glitches and it doesn't crash or freeze. It has been reliable and the performance is good. 

We mostly use the solution for client projects. Across the company, I can't answer how many people use it exactly. We work with customers, so we see it used at the customer end.

We have not experienced any limitations of assets in terms of storage so far.

It's very scalable.

I've never used technical support for GitHub. I can't say if they would be responsive or helpful. 

In terms of the setup, only the clients have you install it on your side. You have some clients that used to access it from the desktop basically, so that is the only place where you have to install the solution.

It's cloud, so you don't need staff for maintenance. It's designing the branches only that you need to worry about. It's like Gmail. You don't need any people for maintaining it.

I don't handle the licensing. I'm not sure how it works or how much it costs. 

I'd recommend the solution to others.

I'd rate it, overall, at an eight out of ten.

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.

I am using it, it was easy to set up and it is working well for me.

I would want to see some form of code security scanning implemented.

Our company has used GitHub for a long time. I have been using this solution for two and a half years.

We use GitLab release 14.6.7.

I did not have any issues with the stability of Github. It worked seamlessly.

I have not contacted technical support.

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.

The initial setup is straightforward.

Client setup takes about 15 to 15 minutes on the workstation where I do my development.

I completed it myself using the documents provided, and I was able to connect it by following the steps.

I would rate GitHub a 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.