GitHub Reviews

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

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. 

The way we can manage the system is very useful. It'd great for managing code. 

You can have the main branch, and then create another branch, and easily merge them together if you like. 

You can effectively manage code reviews by issuing pull requests. Fellow developers can review my code, which helps ensure that the code is written correctly and clean. It's a useful exchange of information. 

The flow process helps us keep our applications stable. The released version is always running smoothly.

Once you get familiar with the system, it's very easy to use.

The product has a very user-friendly interface and user-friendly security.

There is a bit of a learning curve. At first, you'll have to do some searching online to figure out how to perform or reverse certain actions. When we have new team members, they tend to send you a full request for issues and it can create a bit of a bottleneck. There can be a lot of research and lots of problems initially created by users that don't yet understand the system.

The solution could use even more integration with automation tools. 

I've been using the solution for a while.

The stability is quite good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

There are four teams working with GitHub currently in our company.

I haven't had the chance to contact support, and therefore cannot really comment on how helpful or responsive they are. 

Within the company, we have specialized people who are maintaining the server. From my own experience as a software developer, outside the company, using the public community GitHub has on offer and publishing questions to it allows s to find the answers we need. The community is really responsive to us.

Initially, when I first joined the company, they were using another solution, and recently we decided to move to GitHub. We are currently using it on a daily basis.

There are other solutions that we use for source control and they're going to be migrating to GitHub.

I did not really work on the deployment per see. However, it is really easy to create new branches. There are also great opportunities for integration with other tools, for example. There's some great automation, for example, which is helpful.

I personally use the free version. the company has the enterprise version of the solution. I'm not a part of the licensing process internally and therefore do not have details in regards to how much the company pays to use the enterprise version,

We are just customers and end-users.

We are using the latest version of the solution. We have some internal solutions deployed. We have our own private server, a GitHub server, and it always is properly maintained and always updated with the latest version for better performance.

I would recommend the solution, however, I would suggest those who intend to use it get the proper training on it first.

I would rate the solution at a nine out of ten.

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

It's great that GitHub integrates easily with Jenkins. It's helpful for the DevOps as well, checking in and checking out, the solution incorporates well. It's easy to integrate with third parties as well as with other build management tools. It's a really user-friendly tool.

There are some minor areas of improvement that could be made, specifically the onboarding processing which I think could be simplified. It would be great if GitHub could integrate with AI and machine learning systems.

I've been using this solution for two years. 

The solution is stable. 

The scalability is good. We're using it with Microsoft, Docker and Kubernetes, and whenever there's an increase in traffic, we're able to manage that. 

I previously worked on GitLab but find GitHub has many more options and features, particularly in terms of project and SQL management. It was easy to migrate from GitLab to GitHub.

The initial setup is very easy and there are multiple ways to integrate GitHub Dash or to command prompt and that simplifies things. We migrated to pipeline to build and deploy the process. 

I rate this solution eight out of 10. 

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

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

It has a lot of features from the code development perspective. You get a lot of features such as repo, commit, merge, and branch. You can play around and do things on the fly.

It is easy and simple to deploy. It is also easier to use when working from home.

It is currently only from the development perspective. It doesn't have features related to project management and testing. It is not like Azure DevOps. So, there is a lot of room for improvement.

It is a version control product, and it would be good if they can come up with a complete DevOps product.

Its stability is good.

Because it is cloud-based, you don't have scalability-related issues. We have around 30 users.

We didn't have to contact them because it is very user-friendly and easy to use. For any help, you can go to the communities.

Its initial setup is straightforward and easy. It is much easier and simpler than Azure DevOps. This is something that Microsoft has to aim for.

It is open-source. There is no license for GitHub.

If you are a startup or have a small team, it is a good platform to start with because you can achieve your business goal without any cost. It provides a lot of flexibility, and you can structure yourself for any kind of product development.

I would rate GitHub a nine out of ten.