We use GitHub to manage repositories, pull requests from partners and merge new changes.
Software Test Automation Engineer at a manufacturing company with 5,001-10,000 employees
Effective solution for managing version control and changes to code on projects with multiple team members
Pros and Cons
- "The version control 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."
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
The control version functionality for this solution has been most valuable, especially when managing projects with multiple versions.
What needs improvement?
The descriptions within Github could be more user-friendly to show the trees of Gitflow.
Buyer's Guide
GitHub
November 2024
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
815,854 professionals have used our research since 2012.
For how long have I used the solution?
I have used this solution for ten years.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
We have not needed to contact customer service. All the information we have needed has been available on the web.
How was the initial setup?
The initial setup is straightforward.
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
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.
Chief Solutions Officer at CleverIT B.V.
Comes with an Advanced Security model and allows us to create custom actions and deploy to different types of infrastructure
Pros and Cons
- "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."
- "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."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using it for more or less one year.
What do I think about the stability of the solution?
It is, for sure, stable.
What do I think about the scalability of the solution?
It is definitely scalable.
How are customer service and support?
They were very helpful.
How was the initial setup?
I have experience in many tools. GitHub is not the hardest, and it is also not the easiest. It is of medium level.
What other advice do I have?
I would advise trying out the Advanced Security model, which is its best functionality.
I would rate it a 10 out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer:
Buyer's Guide
GitHub
November 2024
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
815,854 professionals have used our research since 2012.
Associate Software Engineer at SNP
Works as a repository but needs improvement in UI
Pros and Cons
- "We use GitHub as a repository."
- "GitHub needs to improve its UI."
What is our primary use case?
We use GitHub as a repository.
What needs improvement?
GitHub needs to improve its UI.
For how long have I used the solution?
I have been using the solution for four years.
What do I think about the stability of the solution?
GitHub is very stable.
What do I think about the scalability of the solution?
The tool is scalable, and we can leverage our DevOps projects using it. My company has 200 users.
How was the initial setup?
The tool's setup is straightforward and takes seven days to complete.
What other advice do I have?
I rate the product a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Architect Lead at a tech vendor with 1,001-5,000 employees
Great availability, easy to expand, and user-friendly
Pros and Cons
- "The solution can scale."
- "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."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I've used the solution for only a year now.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I've never used technical support for GitHub. I can't say if they would be responsive or helpful.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
I don't handle the licensing. I'm not sure how it works or how much it costs.
What other advice do I have?
I'd recommend the solution to others.
I'd rate it, overall, at an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical Director at Optko
Code hosting platform that offers flexible usage that can be ramped up or down
Pros and Cons
- "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."
What is our primary use case?
We use this solution for DevOps activities.
What is most valuable?
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.
What needs improvement?
This solution could be improved by offering crowd sourced support where we could ask questions to other users.
For how long have I used the solution?
I have been using this solution for three years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the 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.
How was the initial setup?
This solution does not require a big installation. It can be used as and when it is needed without a huge commitment.
What other advice do I have?
I would recommend using Githib to others.
I would rate this solution a nine 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.
Software Engineer at a tech services company with 1,001-5,000 employees
User-friendly with a good interface and great for managing code
Pros and Cons
- "The product has a very user-friendly interface and user-friendly security."
- "There is a bit of a learning curve."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I've been using the solution for a while.
What do I think about the stability of the solution?
The stability is quite good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
What do I think about the scalability of the solution?
There are four teams working with GitHub currently in our company.
How are customer service and technical support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
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,
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Cloud Solution Architect at Microsoft
A user-friendly solution with a good feature set and scalability
Pros and Cons
- "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."
What is our primary use case?
We use GitHub whenever there is an infrastructure level deployment on any of the cloud platforms.
What is most valuable?
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.
What needs improvement?
The initial setup and implementation could be easier, I had some difficulties with it at first but I don't have a development background.
For how long have I used the solution?
I've been using this solution for around one year.
What do I think about the stability of the solution?
The solution is pretty stable and straightforward, but having experience helps.
What do I think about the scalability of the solution?
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.
How are customer service and support?
Any issues have been resolved by our own team, but I can say that Microsoft customer support is usually satisfactory.
How was the initial setup?
The initial deployment was straightforward and took three to four months.
What other advice do I have?
I would rate this solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data Engineer at a media company with 10,001+ employees
Software development platform that releases new features and improvements frequently.
Pros and Cons
- "During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently."
- "The security for this solution could be tightened up and improved."
What is most valuable?
Because Github is hosted in the cloud, we do not require many resources to maintain it.
What needs improvement?
The security for this solution could be tightened up and improved.
For how long have I used the solution?
We have used this solution for three years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
We have not needed to contact their support team frequently.
How was the initial setup?
The initial setup was straightforward.
What's my experience with pricing, setup cost, and licensing?
The licensing offered is on an annual basis.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free GitHub Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Popular Comparisons
SonarQube Server (formerly SonarQube)
Veracode
GitLab
Checkmarx One
Snyk
Mend.io
Fortify on Demand
Sonatype Lifecycle
Bitbucket
Qualys Web Application Scanning
Bitbucket Server
Kiuwan
Atlassian SourceTree
AWS CodeCommit
Buyer's Guide
Download our free GitHub Report and get advice and tips from experienced pros
sharing their opinions.