We just raised a $30M Series A: Read our story

GitHub OverviewUNIXBusinessApplication

GitHub is the #2 ranked solution in our list of top Version Control tools. It is most often compared to Atlassian SourceTree: GitHub vs Atlassian SourceTree

What is GitHub?
GitHub is a web-based Git repository hosting service. It offers all of the distributed revision control and source code management (SCM) functionality of Git as well as adding its own features. Unlike Git, which is strictly a command-line tool, GitHub provides a Web-based graphical interface and desktop as well as mobile integration. It also provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.
GitHub Buyer's Guide

Download the GitHub Buyer's Guide including reviews and more. Updated: October 2021

GitHub Customers
Dominion Enterprises, NASA, Braintree, SAP, CyberAgent
GitHub Video

Pricing Advice

What users are saying about GitHub pricing:
  • "It is open-source. There is no license for GitHub."
  • "The private repositories are free, which is very good."

GitHub Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
AA
Vice President at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Good technical support and highly scalable but the licensing is challenging

Pros and Cons

  • "We've found the technical support to be very helpful."
  • "If it had all of the end-to-end integration, then we probably wouldn't have any doubts about what we have installed. However, at this point, we're still trying to figure out how to use it end-to-end."

What is our primary use case?

Currently, the solution is our source control system. We manage the DevOps pipeline for the company and it's the version control backbone.

What is most valuable?

I'm curious as to what DevOps Tools can be integrated into GitHub to get it to be on part with the capabilities that come out of the box in GitLab, or whether we should just switch to GitLab to get all of those capabilities.

The stability is quite good.

The scalability is excellent.

We've found the technical support to be very helpful.

Overall, it's a very good product.

What needs improvement?

If it had all of the end-to-end integration, then we probably wouldn't have any doubts about what we have installed. However, at this point, we're still trying to figure out how to use it end-to-end. 

The new version is supposed to make GitHub actions available to us within the on-prem instance. We're waiting for that, just to see how that plays out with the rest of the source control features and to see if that gives us some semblance of similar capability to what GitLab supposedly provides.

I don't know if there are any plans to do a better integration with the front-end type of tooling. I would like to see it evolve to a full-blown DevOps stacks hopefully similar to GitLab at some point.

We've found the way licensing is set up to be very challenging.  Also, the LDAP sync capability falls over frequently due to the complexity of our LDAP domains.  This requires us to perform manual LDAP syncs almost on a daily basis

For how long have I used the solution?

I'm new to the company. That said, I would guess that the company has probably been using the product for about three to four years at this point. It's been a while. I've used it within the last year and I'm continuing to use it regularly.

What do I think about the stability of the solution?

As far as stability goes, it's been good. We haven't really had a lot of major issues yet. There are no bugs or glitches. It doesn't crash or freeze.

What do I think about the scalability of the solution?

It's obviously very scalable. We have thousands of users on it and there are no concerns.

How are customer service and technical support?

We have a monthly call with the technical sales folks. They look after our every need and they're very technically knowledgeable as well. If we go through support, usually issues are resolved fairly quickly. There are no complaints there. We're very satisfied with the level of support on offer.

How was the initial setup?

I just manage the team. I've not involved in the more technical details. I wasn't present for the implementation process. I can't speak to how easy it was, or how difficult, via any first-hand knowledge. 

What's my experience with pricing, setup cost, and licensing?

The licensing model that they have is annoying. One of the things that we struggle all the time with is people that have left the team or the group. We have lots of application teams that are using GitHub. People are moving constantly between organizations, they're moving to different teams, they're moving out of development. 

There's really not an easy way to track who's still using licenses. If they've vacated the position unless somebody goes back into the active directory and actually removes them from the group, they're still holding onto a seat and we're still trying to figure out, how to manage this so that their seat automatically gets reclaimed when people are moving around and it's not a very straightforward process. It takes a lot of effort on our part to try and keep the inventory seats available and managed properly.

What other advice do I have?

We aren't partners. We are simply customers and end-users.

We are still on the previous version. We are still waiting for more stability from the latest version before we update everything.

It's a great product. That said, it needs some work still to be able to do everything that GitLab can do, for example. I'm not sure what the future plans are for GitHub. I know they're working on adding a lot of capabilities now that they're part of Microsoft. They're probably going to make it a much more robust solution - not just a version control system. My perspective is as an enterprise on-prem user. I don't know from an open-source community standpoint, how they feel about the changes. I'm sure most of the users are pretty happy with it as a hosting platform. However, my need is specific to my organizational uses.

I'd rate the solution at a seven 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.
Flag as inappropriate
Mohan_S
Information Technology Specialist at Brandix
Real User
Top 20
Offers time reduction and enables remote work

Pros and Cons

  • "GitHub provides good time reduction and this is what I value the most."
  • "The security point should be addressed in the next release and scaling is also an issue."

What is most valuable?

GitHub provides good time reduction and this is what I value the most. My team uses GitHub for working remotely. Security is also a good feature of the solution. It's as if the solution creates a security barrier in the server, whereby I can push changes they make to my server once they come to GitHub. 

The solution has a lot of features. Should my developer leave tomorrow, the changes he has made will remain, even as another developer could do the work.

What needs improvement?

The branches created for the separate software and enrollment should be improved. There is a need to create separate software branches, such as for the production, operation and development teams, who are licensed, in respect of their need to match to test what they develop in a test environment. I can immediately go back and look at the features to see if they are up to the mark, such as those involving unnecessary code. 

As someone who works in infrastructure, I know how hard it can be to create things on this level, but it can be worthwhile. Confirmations and requisite future updates are in the end user's domain. The migration of the databases, such as the migration of my websites to the new WordPress sites, works at times but is slow. In such a case, the hardware must be increased. When it comes to the question of whether we should change to new servers and set up a new infrastructure level, I have found GitHub to be very helpful. It pushes the code directly to the repository and dumps the database on the other end. 

The security point should be addressed in the next release. Scaling is also an issue. If the code is very high on the user side and I should suddenly find myself wanting to increase the monthly use of my website from 10,000 to 30,000 people, it can create an imbalance in the infrastructure. In the case of the code level, we may see issues involving optimization. 

For how long have I used the solution?

I have been using GitHub for more than seven or eight months. 

What do I think about the scalability of the solution?

The solution is easily scalable and encourages migration. While I have other products at hand, GitHub makes things fun. We wish to lead and expand. We want to scale this project to the next level, since we have certain customers in hand.

How are customer service and technical support?

I had to make use of technical support two months back, when I first started working and had a learning curve. This was while I was exploring new ideas as relate to my infrastructure experience. When encountering changes to the core side or the scaling, it is necessary to make use of technical support. An abrupt increase can cause problems with the infrastructure, so I am looking for solutions that will not require me to make changes to it each time this should occur. GitHub allows the core to be scaled up with ease and it offers auto scaling. 

How was the initial setup?

There is a certain amount of difficulty involved in the work we did with the developer. This is because we use private repositories, not public ones, for security reasons and this requires the developer to have a code for a secure shell. 

When we do the initial setup in the cPanel, we are supposed to utilize it for our infrastructure. The enrollment is set up to the cloud and the cPanel and GitHub to the local systems, wherever the developer may be found. Usually, they are remote. We have confidence that the developer reposits first to his local system and from there to the cloud and we must execute shell for these development purposes.  

What other advice do I have?

Our initial deployment was with Cloud One. The cPanel is the browser involved. We make use of WordPress.  

GitHub is the perfect tool for use at present and is extremely necessary. It is one of the best solutions out there. Apart from GitHub, you need to use the local Git version control system since it involves code on a cloud platform. Git version is very helpful. One could download the large types of codes to do on the core level so that there will not be a need to go to the cloud setup every time. The code commands can be run from the local system. Setup and migration can be done with ease. The person would set up the order and the view. In my experience, GitHub is very easy to operate. 

I rate GitHub as a perfect ten out of ten. 

I previously used different tools. At present, I am utilizing GitHub and providing assistance with cell phone numbers. The solution allows me to make workspaces and perform changes with ease. It also allows for easy monitoring. I receive updates from Slack for confirmation purposes. There is no need to wait on my developers, as a connection can be made with the production server. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
541,462 professionals have used our research since 2012.
Ali Albousaifi
Information Technology Consultant @ CIM at Group
Consultant
Top 10Leaderboard
Very good solution for process automation and team collaboration

Pros and Cons

  • "The features that I have found most valuable are that it can support you for most of the road map and it can automate some tasks which works really well with collaboration with the teams. They are really interested in how they organize the history of the code itself which is good."
  • "The project management sector really needs some improvement for GitHub. I don't know if GitHub made sense for me as a project manager."

What is our primary use case?

My primary use case for GitHub is for my private projects that I'm developing for my customers. Some customers have their own developers and I sometimes support them to achieve their goals. So we share everything. We're also using GitHub for the documentation for the teams. I also give lectures for the organizations because sometimes they have development teams but they are not qualified enough, so I have to give them some training on it.

What is most valuable?

The features that I have found most valuable are that it can support you for most of the road map and it can automate some tasks which works really well with collaboration with the teams. They are really interested in how they organize the history of the code itself which is good.

What needs improvement?

In terms of what could be improved, I would say the security. I didn't try the two-factor authentication so I don't know if they have it already or not.

I sometimes found it very difficult to connect it with other tools, such as Jenkins or others. For the testing for example, I have to go between both sides. I don't know if I am using it right, but I don't know if they have these features or not. So I have to find other tools to support it because I couldn't really rely on GitHub for the steps that I needed.

Additionally, we are facing really big issues with the Arabic language in GitHub and I don't know if they are focusing on some improvement in the language capabilities. This is one of the things we're facing. 

As I mentioned, for the management we need some improvement in GitHub. It's not built for that. We really need some improvement for the project. It made it tough.

But overall I didn't find anything really urgent needed to improve.

For how long have I used the solution?

I have been using GitHub for about eight years now.

I'm always using the latest update. In my service behavior I always update all the solutions.

What do I think about the stability of the solution?

GitHub is very stable.

What do I think about the scalability of the solution?

Since I am working as a contractor in our organization and I'm doing the development work as a site project manager, I don't have a fixed team. But we can say that for each project it's about 10 to 20 people using GitHub most of the time.

It is used on a daily basis.

It is easy to add new users.

Which solution did I use previously and why did I switch?

I was previously using Jira and Bitbucket but now I'm 100% in GitHub. I switched because of my team - they didn't work on Bitbucket. This is the reason I left Bitbucket even though GitHub is more costly.

I was looking for a management tool. Of course, Jira is the first try. When I looked at it for the cloud there were two options - GitHub and Bitbucket. But when comparing Jira's license to the licenses for Bitbucket or comparing the price between Bitbucket and GitHub, I found it's really cheaper for me to have Bitbucket. But because my team was most familiar with GitHub I decided I had to go with it.

The project management sector really needs some improvement for GitHub. I don't know if GitHub made sense for me as a project manager. But for what it was, it's a really good tool.

How was the initial setup?

The initial setup was okay. It is not really difficult from my perspective.

It is so easy. It took about five minutes maximum. It was really easy to configure. But, as I told you, I couldn't figure out how I can use it with my local IDE or development IDE like VSCode or something like that. That's why I'm using Jira. If I use Jira I couldn't change the issue from GitHub to task. In GitHub I found it to be difficult with this.

What about the implementation team?

I did the installation myself.

What other advice do I have?

My recommendation for anyone thinking about GitHub is that it is the best solution - except for the price.

On a scale of one to ten, I would give GitHub a nine.

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?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
HB
Software Engineer at a tech services company with 1,001-5,000 employees
Real User
Top 5Leaderboard
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.
Flag as inappropriate
XQ
Technical Lead at a tech services company with 51-200 employees
Real User
Top 20Leaderboard
Great code sharing and capability to roll back to a previous version; enabled CICD pipeline

Pros and Cons

  • "The code sharing and updated history are valuable features."
  • "Could be more user friendly."

What is our primary use case?

Our primary use case of this solution is for collaboration, code sharing, and as a testing environment. We can put it into Docker and create images. I'm the technical lead in the company and we are customers of GitHub. 

How has it helped my organization?

GitHub has enabled the CICD pipeline. Without GitHub, we wouldn't be able to do that. 

What is most valuable?

The code sharing and updated history are valuable features, the capability to roll back to a previous version is very useful. We're also able to make a branch and a merge and it's easy to collaborate with our teams. We can hook up with Jira, with Wiki, and OpenAPI. We have access to all the features we require right now.

What needs improvement?

I'd like to GitHub become a more user friendly solution. There are some commands that if we want to reset it to a previous version or we try to roll back, we sometimes get a broken link in the history. Maybe there's something we can do to make the learning curve easier for the user. Perhaps by visualizing the operation instead of the command line.

For how long have I used the solution?

I've been using this solution for seven years. 

What do I think about the stability of the solution?

The solution is quite stable, we haven't had any crashes.

What do I think about the scalability of the solution?

We don't require much scalability. There's the tech team and then we have around 100 developers, managers, some architectural cloud engineers, and a test engineer. They all use GitHub. We don't require maintenance but we have a cloud engineer who is mainly on AWS services. The only thing that I think they need to deal with is generating tokens for new users. We use the solution extensively.

Which solution did I use previously and why did I switch?

I have previously used SVN but I prefer GitHub, it seems to be more powerful than SVN. We have a centralized website and a better user interface. 

How was the initial setup?

There's no real setup required, we just installed it and hooked it up to our project, and we put it into the Docker file. Not much setup.

What's my experience with pricing, setup cost, and licensing?

We pay an annual license fee.

What other advice do I have?

This is definitely the best solution I have tried so far. That said, I believe it has some space to improve. It's important to do some homework before implementation and I would suggest using the documentation posted on GitHub. 

I rate this solution an eight out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
SK
CTO at Cantier Inc
Real User
Top 5Leaderboard
Open-source, stable and scalable, and user-friendly with lots of features

Pros and Cons

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

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

What do I think about the stability of the solution?

Its stability is good.

What do I think about the scalability of the solution?

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

How are customer service and technical support?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

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.
Flag as inappropriate
Mykola Pelyp
DevOps - CoE Critical Services at a tech vendor with 5,001-10,000 employees
Real User
Top 5
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.
ZW
Enterprise Architect at a tech company with 10,001+ employees
Real User
Top 10
Stable solution for version control and source code management

Pros and Cons

  • "The most valuable feature is the source code management. It's very helpful and it's a great product."
  • "If you are uploading or cloning a large file, with more than 25 megs, it's pretty slow."

What is our primary use case?

The primary use case of this solution is for version control and source code management.

What is most valuable?

The most valuable feature is the source code management. It's very helpful and it's a great product.

What needs improvement?

If you are uploading or cloning a large file, with more than 25 megs, it's pretty slow.

The upload/download speed is pretty slow for a single large file. It is only a problem if the repo has a high-resolution pic or video.

For how long have I used the solution?

I have been using GitHub for three years.

What do I think about the stability of the solution?

This solution is quite stable.

We have over 1,000 users that use this solution daily.

How are customer service and technical support?

We very seldom need support.

Which solution did I use previously and why did I switch?

Previously, we were using Bitbucket. We switched to GitHub because it is the number one source code management platform, and it has the cooperation of the open-source community. It provides for better collaboration. We all participate in the open-source community.

There are more users on GitHub, compared to Bitbucket.

How was the initial setup?

The initial setup is quite simple. It took less than an hour and could even be done in as little as 15 minutes.

What about the implementation team?

The server was set up with support from the team in the development center of the office. It's GitHub, so you don't need a special consultant for it.

What other advice do I have?

I would recommend this solution to organizations that are looking for a platform to manage source code.

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.