GitHub Reviews

GitHub is used to store my source code or raw reports.

The most valuable features are GitHub are the standard features, they are very useful.

GitHub could improve by being more user-friendly.

I have been using GitHub for approximately 15 years.

GitHub has high availability.

I have not used the support from GitHub.

I have not used another solution prior to GitHub.

I would recommend this solution to others.

I rate GitHub an eight out of ten.

We use this solution to manage and store our development work.

This product allows us to easily collaborate on development tasks with our subcontractors, and control the workflow as the project progresses.

We would like this solution to have a more user-friendly interface.

We have been working with this solution for two years.

We have not encountered any issues with the stability of this solution.

We have found this to be an easily scalable solution.

The initial setup for this solution was very straightforward.

We also evaluated Microsoft TSS.

I would rate this solution an eight out of ten.

We use this product to host the code base for different development teams within our organization and for versioning the codes and integrating with CI/CD tooling. We have a partnership with GitHub and I'm a product manager. 

Using GitHub has been beneficial for us because it was an easy process for users and it has improved efficiency. In contrast to Bitbucket or Azure Repos, moving things over to GitHub was simple.

We like the simplicity of GitHub and that it is free of complications, as opposed to other tools on the market. Its ability to be integrated with third-party softwares such as Azure Pipelines or Jenkins, is great.

The solution lacks sufficient support in terms of professional services that could be provided proactively to customers. The product documentation could be improved. What currently exists on the GitHub website is not complete and not sufficient to help end users with customizations or integrations, tools for code quality, or app security. In the next release, I would love to see something around security as well as some code analysis and open-source vulnerability detection features. It would be helpful if there was a better DevOps offering from GitHub. GitHub Actions is still maturing.

I've been using this solution for two years. 

The solution is stable. 

GitHub is scalable, we have around 120 users. They are mainly software developers and engineering managers. We have three people, DevOps engineers and support engineers, working with GitHub and we're likely to expand usage. 

Our technical support experience has been quite good in terms of response and expertise.

Positive

We previously used Bitbucket and Azure Repos. We switched to GitHub because of its ease of implementation and ease of onboarding new users, as well as its integration with third-party tooling.

The initial setup was straightforward. We are in a regulated industry with a large volume of organizations, and there are additional processes that need to be taken care of. Taking all that into account, the deployment took about 10 days. Implementation of GitHub alone just takes a few hours. We worked with a third-party vendor. 

The product certainly saves us a lot of time and that equals money. We save time in terms of how the code base can be managed and versioned. We have better control over the release of the product, and we have reduced the time that takes. We're getting a good ROI. 

I recommend this solution even though it does not provide the complete suite. There are DevOps services coming in from Microsoft, for example, and you need to go to GitHub Actions separately. Source code management is better on GitHub and I would rate that higher.

Overall, I rate this solution seven out of 10. 

We use GitHub to share the source code and can give users different permissions to use different parts of the project. Whenever a developer changes a source code, it can push it easily, and others can see the change and who made it.

It is a very good solution. GitHub allows the backup of our source code. So we are sure that if all the computers in our company crash and the hardware fails, we can access our code on GitHub. Also, in the past, every repository we built was publicly available to anyone, and others could see our source code, but now we can make a private repository and share it with our team. This feature is very valuable and good for us.

It is very tricky to work with GitHub. For example, it is difficult to merge a code or restore it to an older version. It would be great if they provided a tool that merges the code better and more intelligently.

We have been using this solution for ten years.

It is very stable. Whenever it is connected, it always works, and we love it.

It is scalable. We can easily extend to team members, with a team of about six or seven people in a GitHub repository. Most users are developers, but we can also provide viewing access to others. We don't have any distinct plans to increase our usage of GitHub.

We have not used technical support because GitHub has a large community of users, so if there is an issue, we can find the solution on Google.

We did not use any other solutions before GitHub.

The initial setup was very easy.

It is a free solution. 

I rate this solution a ten out of ten. I recommend GitHub to others to back up their source code or share it among different people on the same project. GitHub is integrated very well with Microsoft Visual Studio and .NET. For example, if we make a project inbox for Visual Studio, we can push the code to GitHub by adding our account to Visual Studio.

Basically, it's just a repository for software developers. Users are able to push their source code and share their code.

I'm able to access any repository that I like, whether it's public or private. That said, for private repositories, I'll obviously need access from the other developer. It's nice that they have the option for public or private repositories.

The collaboration is really great. It has really worked and has really helped me a lot. I find that it is a very important feature.

There is a bit of a learning curve. The very first them that I used it, my issue was understanding it. It seemed very complex to me. That said, eventually, I got the hang of it. They could make it a bit more user-friendly. 

When I was a software developer, I used GitHub a lot. I've used it for the last three years at this point. 

The solution has been stable. 

I was using the solution for my own personal projects.

It supports growth. The platform has very many developers in the world, millions and millions of developers, so it's pretty much scalable.

Technical support could be better. You quickly realize that most of the time, it is other users that are offering new support, not the actual GitHub team.

Neutral

I did not use other repositories previously. 

There's no installation. However, you'll need other tools to help you with pushing the code to GitHub. Once you create your account and log in, it gives you the steps you are meant to follow, so that's good. It helps a complete beginner get started. They'd never get stuck.

I have no visibility in relation to what the costs are surrounding this product.

I'd rate the solution seven out of ten. 

Our organization uses GitHub for version control.

GitHub allows you to create pages, if you want to share documents you can create articles and diagrams with GitHub and share.

On a personal level, GitHub assists you to create your own website.

GitHub uses basic configuration, but messaging is not clear. For example, when a database denies a username and password, it says "asking for person accepted".

I would like to see improvements with merging code from multiple branches. When more than one developer is working at the same time, it becomes complicated. It very much depends on the person doing the merging. There is no assistance from the tool itself. If a mistake is made, the tool will not be able to correct it. It would benefit from an automated checker.

I have been working with GitHub for five years.

The solution is stable.

GitHub is scalable. Our organization has 1,000 people. Approximately 80% would be using GitHub.

The initial setup of GitHub is very simple.

I would give GitHub a nine out of ten overall.

We are using GitHub as a repository for a couple of customers to be able to do Infra as Code in Microsoft Azure for them.

The most valuable features of GitHub are the ease of integration into Microsoft Azure DevOps. The process that you need to deploy into Microsoft Azure becomes fairly simple and the templates are already available, a lot of the engineers find it easier to use.

GitHub could have better integration or capability with other solutions.

I have been using GitHub for approximately four years.

GitHub is highly stable. Our team has not had any trouble with it.

The scalability of GitHub is good. I have not come across any limit.

We have six people using this solution in my organization. We have plans to increase usage.

I have not used the support from GitHub.

The initial setup of GitHub is simple. The full implementation took approximately a few hours. There was some user configuration that took some time.

We did the implementation in-house for GitHub.

 The licensing model from GitHub is very clear.

I recommend this solution to others. There may be some customers that are very picky about not having code on the cloud, and then my recommendation would normally be to use Microsoft Azure Repos, which is essentially a clone of GitHub but it stays within your subscription and within your tenancy on Microsoft Azure.

I rate GitHub a nine out of ten.

We use GitHub instead of our regular shared drive. It offers instant access to shared folders as well as good security.

The GitHub repository needs an upgraded user interface and overall UI improvements. In Automation Anywhere, we have one repository where you can download or upload information. They have two interfaces in a single view that has verification. It would be good if Github offered the same. 

I have been using this solution for five years. 

This solution is somewhat stable, but requires additional supporting products.

This is a scalable solution. We have more than 2,000 users.

I would rate this solution a seven out of ten.