GitHub Reviews

We use GitHub for source control.

GitHub is convenient and easy to use.

GitHub should provide more integration in their next release, including integrating with Jenkins, CI/CD and Jira.

We have been using GitHub for two years.

GitHub is a stable solution.

The solution is scalable. We have approximately 200 users.

Prior to using GitHub, we used Subversion, or SVN and CVS. We switched to GitHub because of the cloud enablement as well as the ease of use.

I would recommend GitHub to anyone considering implementing the solution into their organization. 

Overall, I would rate GitHub a nine out of 10.

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 are actually working with MuleSoft, and for that, we have to build our application. We are working for a company offering hotels and resorts. We are using GitHub for that process. We're building applications on it. 

It's good for branching and keeping the code. Overall, it is a good tool. We can find stable branches there and it is very easy to manage code there.

The interface is good.

We have found that it does allow for helpful integrations. 

It is really simple to set up.

They need to make it possible to recover branches. For any of the branch that does not have PR, that is unrecovered. So there should be an option to recover those branches.

I cannot recall coming across any missing features. 

The user interface on GitLab is better.

I've been using the solution for six or seven months. 

The solution is stable. There are no bugs or glitches. The performance is reliable. It doesn't crash or freeze. 

We have 70 to 80 users on the product currently. We use it on a daily basis.

It's very easy to scale as needed. 

I've never directly contacted technical support. As a developer, I'm not the one who would be contacting technical support. If there were issues, someone else in the company would deal with them. 

I previously worked with GitLab. They are pretty much the same. GitLab does have a very good user interface. That's the main difference.

The initial setup is simple and straightforward. it is not overly complex or difficult. 

As it is a solution that is on the cloud, there is no manual maintenance required. 

We do have a separate team that handles deployment. I don't handle deployments directly myself. 

I don't deal with licensing. I cannot speak to the exact pricing. 

I'm just a customer and an end-user. 

We currently work with the latest updates of the product. 

I'm a developer and I don't work with managing everything on GitHub. I just use it for putting in the code and merging branches.

GitHub actually is a pretty easy tool. It is not very difficult to understand. It is very easy. Everyone can set up branches there or work on it.

I'd rate it eight out of ten. If we could recover branches, I'd give it a perfect ten. 

We use GitHub for versioning and to provide a place on the cloud to store code so that people can work on it together.

The most valuable features are the Git Hooks and SSH keys.

The Projects Tab, which shows you the todo list and the progress for projects, is very helpful.

I would like to see integration with Slack such that all of the changes made in GitHub are reflected there. You would simply enter the Slack URL and the notifications about code changes would be forwarded.

We have been using GitHub for at least a year.

There were a few cases when we were unable to reach GitHub but for the most part, it is stable.

We have different people in the company who are working on different projects on GitHub. It is safe to say that we have about 50 people in total who are using the platform.

I have not been in contact with technical support. With respect to community support, I have noticed that it is pretty evolved. I have used it often and find that it is very useful.

We used to use BitBucket, but when Microsoft announced that private repositories would be free on GitHub, we switched.

The initial setup is super easy.

The private repositories are free, which is very good.

GitHub is definitely a platform that I recommend people use.

I would rate this solution a ten out of ten.

GitHub is essentially a repository of code. It's where you source your code with the client and allows you to use Git. You get versioning and everything else for multiple deployments or codes. That's how we use it.

We stopped the development code on our machines, and we moved everything to GitHub. So, everyone is working on the latest code no matter what we do.

The accessibility is free.

There is room for improvement in terms of interface because  I had a problem with developers who didn't know what GitHub was, and it was a little bit strange to explain. 

I have been using GitHub for three years. We use the latest version. 

I would rate the stability a ten out of ten.

The scalability is very good. It has never let me down.

The initial setup is okay. You need to know what you're doing.

I saw 100% ROI. 

Price is free. 

It is way better than developing software by yourself. I would definitely recommend using the solution.

Overall, I would rate the solution a ten out of ten.

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. 

We use GitHub for code versioning; with multiple developers working on the same projects. It gives us a central source for our code. We commit our code to the cloud using the API called Gita, which tracks which developers have uploaded the code, which have changed it and so on. 

The code versioning is excellent, and having a detailed log, including every change made to the code by every developer, is invaluable. It makes it so that if there is a bug or problem in the product channel, we can find exactly where it happened and how to fix it.

There can be conflict issues when two developers work on the same file or line of code, and it would be great to see that improved, possibly with an AI solution. 

A great feature would be the AI for code conflicts, enabling us to choose which code edit is the one we want to go with. 

I've been using the solution for about eight years. 

GitHub is stable, and they are improving in terms of security. 

The product is scalable. We have about 20 end users in total. 

The support is average; they can be inconsistent and it would be good if they were more responsive. 

Neutral

The initial setup is a little complex because it requires some knowledge of GitHub and code versioning. Certain steps need to be taken in a specific order, and if any are skipped or done wrong, it can lead to failure. Aside from the mentioned challenges, one staff member can complete the setup.

There is sufficient documentation to help with the setup process.

The setup was implemented in-house. 

GitHub is an open-source product, but when using the free-to-use version, anyone can see the code we're working on.

If you purchase a license, there's an option to make your code private, and our organization has a license.

I would rate this solution a nine out of ten. 

Compared to the competition, I would say GitHub is the best, as it has the most robust security, and most of the developer community is familiar with it. Bitbucket is also an excellent solution with solid security, but more developers would require training.

We are using GitHub for the development environment. After we develop some applications, we are pushing actually on both settings. 

I would like to see more security where a plugin was available for us to update in relation to security.

I have been using GitHub for the past seven years.

We are finding GitHub is very stable. Because it is the one that we are actually using on the cloud, it is easy for actual resources.

We currently did not choose the option with the subscription, but the free version actually provided by GitHub and GitLab is acceptable for us. Maybe the institution wants to increase the number of developers to twenty from what we currently have three, then definitely we will increase and prefer to have additional services from GitHub as well as GitLab.

Technical support is excellent on a scale of one to ten I give technical support a ten.

Positive

The initial setup is straightforward and easy. For someone who has actually good experience in software development, including using a repository solution, I think it is easy. Beginners need to refer to the manual and see some online tutorials to receive assistance so that it is easier for them to setup.

You can do the deployment in-house without a problem.

We are currently paying nothing for GitHub.

I think I remember Tortu was the name of the product. There is a Q Balance in our repository providers. I think that one is Microsoft. I do not know exactly, but we are not using it. We tried it but we returned to GitHub.

If you are working in development I would recommend using GitHub. I would rate GitHub a ten out of ten.