GitHub Reviews

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.

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.

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

Because Github is hosted in the cloud, we do not require many resources to maintain it. 

The security for this solution could be tightened up and improved. 

We have used this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

We have not needed to contact their support team frequently. 

The initial setup was straightforward. 

The licensing offered is on an annual basis. 

During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently. How useful these features are, depends on each business. 

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