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.
Cloud Solutions Architect at gwcloud.company
Highly stable and scalable solution
Pros and Cons
- "I would rate the stability a ten out of ten."
- "There is room for improvement in terms of interface."
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
The accessibility is free.
What needs improvement?
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.
Buyer's Guide
GitHub
December 2024
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,019 professionals have used our research since 2012.
For how long have I used the solution?
I have been using GitHub for three years. We use the latest version.
What do I think about the stability of the solution?
I would rate the stability a ten out of ten.
What do I think about the scalability of the solution?
The scalability is very good. It has never let me down.
How was the initial setup?
The initial setup is okay. You need to know what you're doing.
What was our ROI?
I saw 100% ROI.
What's my experience with pricing, setup cost, and licensing?
Price is free.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Penetration tester at KNBS (Kenya National Bureau of Statistics)
Offers public and private repositories and is great for collaboration but there's a learning curve
Pros and Cons
- "I'm able to access any repository that I like, whether it's public or private."
- "There is a bit of a learning curve."
What is our primary use case?
Basically, it's just a repository for software developers. Users are able to push their source code and share their code.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
When I was a software developer, I used GitHub a lot. I've used it for the last three years at this point.
What do I think about the stability of the solution?
The solution has been stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I did not use other repositories previously.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
I have no visibility in relation to what the costs are surrounding this product.
What other advice do I have?
I'd rate the solution seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
GitHub
December 2024
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,019 professionals have used our research since 2012.
Software Engineer at Infosys
Easy to install, and has good documentation
Pros and Cons
- "I did not have any issues with the stability of Github. It worked seamlessly."
- "I would want to see some form of code security scanning implemented."
What is our primary use case?
I use Github to store the code that I write. I don't use it very much. It may be used more by the active developers.
What is most valuable?
I am using it, it was easy to set up and it is working well for me.
What needs improvement?
I would want to see some form of code security scanning implemented.
For how long have I used the solution?
Our company has used GitHub for a long time. I have been using this solution for two and a half years.
We use GitLab release 14.6.7.
What do I think about the stability of the solution?
I did not have any issues with the stability of Github. It worked seamlessly.
How are customer service and support?
I have not contacted technical support.
Which solution did I use previously and why did I switch?
Some of these tools are associated with our parent company. We consume them. I believe they were set up by our parent company's tools team.
How was the initial setup?
The initial setup is straightforward.
Client setup takes about 15 to 15 minutes on the workstation where I do my development.
What about the implementation team?
I completed it myself using the documents provided, and I was able to connect it by following the steps.
What other advice do I have?
I would rate GitHub a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Security Architect at a computer software company with 1,001-5,000 employees
Cost-effective and provides good customization and support
Pros and Cons
- "The solution provides good customization and support."
What is our primary use case?
We use GitHub for AI features.
What is most valuable?
GitHub is a cost-effective solution. The solution provides good customization and support.
For how long have I used the solution?
I have been using GitHub for a couple of years.
What do I think about the stability of the solution?
We haven’t faced any stability issues with GitHub.
How was the initial setup?
The solution’s initial setup is straightforward.
What's my experience with pricing, setup cost, and licensing?
GitHub is a cost-effective solution.
What other advice do I have?
GitHub's branch protection feature is effective in our workflow management. I work with the cloud version of GitHub. The documentation is enough to resolve issues with the solution. People working with Microsoft tech can use GitHub. Microsoft is investing heavily in this tool. Using GitHub depends on users' use cases and their technologies.
Overall, I rate the solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Sep 9, 2024
Flag as inappropriateSenior Lead Mobile App Developer at a financial services firm with 11-50 employees
A stable and scalable solution with robust security and excellent logging functionality
Pros and Cons
- "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."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I've been using the solution for about eight years.
What do I think about the stability of the solution?
GitHub is stable, and they are improving in terms of security.
What do I think about the scalability of the solution?
The product is scalable. We have about 20 end users in total.
How are customer service and support?
The support is average; they can be inconsistent and it would be good if they were more responsive.
How would you rate customer service and support?
Neutral
How was the initial setup?
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.
What about the implementation team?
The setup was implemented in-house.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Chief Web Application Architect at Dbitpro, llc
A mature and polished solution with excellent functionality, and highly scalable with great customer support
Pros and Cons
- "The versioning of the code and the tracking of changes are definitely some of my top features."
- "The solution could have better support for the Markdown language."
What is our primary use case?
We use the solution when developing new code or modifying existing code, changes are tracked and other team members can review the code before production.
How has it helped my organization?
The ability to track external changes to repositories we are using has been very useful for us. If we have a piece of code that's being implemented and it makes use of modules that we're calling externally from, let's say NPM, and a defect is found in one of those NPM modules, we're immediately alerted that a defect has been found in libraries outside of our code space. This enables us to keep in touch with defects that other people have discovered in the code that we're using. GitHub informs us as other users discover broken code, which allows us to deal with issues very quickly, without investigation on our part.
What is most valuable?
The versioning of the code and the tracking of changes are definitely some of my top features.
The ability to code reviews with peers.
The automatic checking to make sure that any of the code in my repository is not out of date with any modules that I'm making use of.
What needs improvement?
The solution could have better support for the Markdown language.
For how long have I used the solution?
I've been using the solution for over ten years, probably since its beginning.
What do I think about the stability of the solution?
The solution is very stable, they have been working on it for over a decade.
What do I think about the scalability of the solution?
The product is extremely scalable. We've seen applications that are hundreds of thousands of lines of code and it doesn't have any problems working with them.
I'm a contractor for the Department of Veteran Affairs, and we've easily got several thousand people making use of the code just within the VA itself. It's being used by almost everyone on a product development team, including project managers, testers, developers, and documentation specialists.
How are customer service and support?
The support is very good. We make use of Slack for communication and we have dedicated technical support for GitHub right in our Slack, which allows us to get responses within minutes from their technical support team.
How was the initial setup?
The initial setup was very simple.
It really depends on the application we're working on. I've seen deployments take as little as 15 or 20 minutes to push out a code change, up to hours or days depending on the functions that we're changing.
What about the implementation team?
We implemented the solution via an in-house team.
Due to the cloud environment, we don't need anyone for maintenance, that's all done by GitHub.
What's my experience with pricing, setup cost, and licensing?
We have an enterprise licensing agreement, and I am not part of the finance department so I can't say how much it costs.
What other advice do I have?
I would rate GitHub a nine out of ten.
The implementation is a hybrid public and private cloud. GitHub in some ways is similar to NPM, but it is a code repository primarily for code versioning systems. It's all cloud-based and we just upload our code to it. There are functions within GitHub that will take and monitor the code that's uploaded and any NPM repositories that it makes use of, and confirms that your code is making use of the latest code repositories. Anytime there is a discrepancy or an upgrade to one of the code repositories, it lets you know what that upgrade is.
They're constantly making improvements to the environment, adding new features and functionality. The new features and functions that they're coming out with are available to me sometimes before I realize I even need them.
We use GitHub extensively with any new product we are developing and we're going to keep doing it that way. I would advise anyone to implement this solution.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Staff Engineer at a wireless company with 10,001+ employees
Code hosting platform used to successfully manage distributed systems and facilitate remote collaboration
Pros and Cons
- "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."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
This solution could be improved if migration was fully automated to make it easy, for example, to migrate repositories into GitHub.
For how long have I used the solution?
I have used this solution for eight years.
How are customer service and support?
The customer service for this solution is not great. The team either takes a long time to respond or doesn't respond at all.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
The initial setup is straightforward and only involved four to five steps.
What other advice do I have?
I would rate this solution a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Azure DevOps Engineer at SoftServe Ltd.
Git Hooks and SSH keys are useful, and storing projects in private repositories is free
Pros and Cons
- "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."
What is our primary use case?
We use GitHub for versioning and to provide a place on the cloud to store code so that people can work on it together.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using GitHub for at least a year.
What do I think about the stability of the solution?
There were a few cases when we were unable to reach GitHub but for the most part, it is stable.
What do I think about the scalability of the solution?
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.
How are customer service and technical support?
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.
Which solution did I use previously and why did I switch?
We used to use BitBucket, but when Microsoft announced that private repositories would be free on GitHub, we switched.
How was the initial setup?
The initial setup is super easy.
What's my experience with pricing, setup cost, and licensing?
The private repositories are free, which is very good.
What other advice do I have?
GitHub is definitely a platform that I recommend people use.
I would rate this solution a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free GitHub Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Popular Comparisons
Bitbucket
Bitbucket Server
Atlassian SourceTree
AWS CodeCommit
IBM Rational ClearCase
Liquibase
Helix Core
Surround SCM
Apache Subversion
Buyer's Guide
Download our free GitHub Report and get advice and tips from experienced pros
sharing their opinions.