GitHub Reviews

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 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 are satisfied with the performance, and we've never had any performance issues because we generally use it on a smaller scale. Using the solution feels like we are running a massive development team comprising a couple of other employees and me. We design the environment and can manage the branching and design better.

There could be more integration into Azure. It will make it easier for us to present it to customers.

We have been using this solution for about three years.

It is stable, and we've never had issues.

It is on cloud, so it is pretty scalable. We use it in the consultancy department to test and see customer environments and errors. It is also good when doing a cause analysis because you can see the code that is being used.

The initial setup was easy.

It is a free solution.

I rate this solution a seven out of ten. I would recommend GitHub, but Visual Studio is arguably a bit better.

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.

Tutorial videos within the GitHub dashboard will very helpful.

I have been using this solution for one year. 

This is a stable solution. 

This is a scalable solution. We have between 300 to 400 users. There are five DevOps staff in our team who take care of maintenance.

This is an open source solution and does not include licensing. 

I would rate this solution 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. 

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 find GitHub very user-friendly.

Nothing is coming to my mind that needs to be improved with GitHub.

As of now, if I would like to learn about GitHub or its features, I would have to look on YouTube. It would be nice if they were able to send out a newsletter with explanations of new features that they are offering and what features are available.

I have been working with GitHub for four to five years.

GitHub is a very stable solution.

GitHub is scalable. We are more than 200 individuals, in many countries.

The setup of GitHub is very simple if you have a knowledge of Linux and follow the process document. 

We have the licensed version of GitHub.

We have Bitbucket and it is pretty good. 

GitHub can integrate with AWS, Azure, and Google Cloud. If you are using a VPN, the integration will be more difficult. I would rate this product an eight 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.