GitHub OverviewUNIXBusinessApplication

GitHub is the #2 ranked solution in top Version Control tools and #3 ranked solution in application security solutions. PeerSpot users give GitHub an average rating of 8.6 out of 10. GitHub is most commonly compared to Atlassian SourceTree: GitHub vs Atlassian SourceTree. GitHub is popular among the large enterprise segment, accounting for 63% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a comms service provider, accounting for 17% of all views.
GitHub Buyer's Guide

Download the GitHub Buyer's Guide including reviews and more. Updated: November 2022

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 Customers
Dominion Enterprises, NASA, Braintree, SAP, CyberAgent
GitHub Video

GitHub Pricing Advice

What users are saying about GitHub pricing:
  • "If there are only 10 people using a particular repository, then GitHub is free. But if we increase the number of users, we need to pay the normal charge for GitHub."
  • "We have an enterprise licensing agreement, and I am not part of the finance department so I can't say how much it costs."
  • 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
    Athmabhuthi H - PeerSpot reviewer
    Managing Consultant at Wipro Limited
    Real User
    The forking feature allows us to release a specific set of features to the environment.
    Pros and Cons
    • "The most valuable aspects of GitHub are version control and parallel development. I also appreciate the forking part, which allows us to release a specific set of features to the environment."
    • "The development team pushes the code into a repository, and the CI/CD pipeline will perform the build. We need open-source libraries to perform the builds. It would be helpful to have the ability to link to open-source libraries like npm libraries. I don't know if GitHub Actions provides this. I would like to see that in GitHub Actions if they don't."

    What is our primary use case?

    Our customer has hundreds and thousands of applications, and 12 are part of my current project. Three of those applications are using GitHub as a code repository. The rest use Bitbucket. This customer is an Atlassian shop, so only I don't think more than 50 people use it.

    Any code they develop will be version-controlled in this GitHub tool, and they use the branching and merging strategy to promote their code. We use it for version control and parallel development.  

    The code in GitHub will be consumed by CI/CD pipeline for the build and deployment. We're using the latest version, which has a feature called GitHub Actions that enables CI/CD within GitHub, but this organization doesn't use GitHub Actions. They prefer Bamboo. 

    What is most valuable?

    The most valuable aspects of GitHub are version control and parallel development. I also appreciate the forking part, which allows us to release a specific set of features to the environment. 

    Development teams can integrate this tool with their IDEs. GitHub provides command line instructions that should suffice. But customers wonder how to configure their IDE because you have to clone the repo, register the username with a password, and then switch. All those things need to be performed within the IDE. So I don't know whether those things are already available. That would enable the developer to integrate their IDEs with the GitHub repository.

    What needs improvement?

    The development team pushes the code into a repository, and the CI/CD pipeline will perform the build. We need open-source libraries to perform the builds. It would be helpful to have the ability to link to open-source libraries like npm libraries. I don't know if GitHub Actions provides this. I would like to see that in GitHub Actions if they don't. 

    If you know the language for your build, it would be wonderful if GitHub automatically provided the link to those language-specific libraries so we don't need to search for the library. 

    For example, if I'm using Node.js, I should be in a position to link it to the npm libraries associated with that version so my build using the CI pipeline will work well. Then the results in the library must go into an artifact repository. We'll have to depend on JFrog or Sonatype to provide binary repositories. Git has the repository technology, so why not offer a binary repository feature?

    GitHub has a static code repository; now, GitHub Actions provides CI/CD. The resulting packages should stay somewhere. I don't know whether they have added this or not because I have not explored the GitHub Actions. They're all public libraries, and the result of the build or CI pipeline is a deployment-ready package. Where will we keep them? That's where we need a binary repository.

    In addition to the binary repository, I think they could also include some vulnerability scans to ensure the code we deliver is clean. SonarQube is a static code analysis we use. There are tools coming from Fortify or Veracode that can ensure there is no security vulnerability in the code. It's a complete CA practice-related tenant. It would be wonderful if they could add this functionality.

    For how long have I used the solution?

    We've used GitHub since 2013. 

    Buyer's Guide
    GitHub
    November 2022
    Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    657,849 professionals have used our research since 2012.

    What do I think about the stability of the solution?

    GitHub performs well with the current load. I haven't had issues with the tool. 

    What do I think about the scalability of the solution?

    We've never had an with the number of projects or developers using this tool. We've consistently had around a thousand developers over the years. The load will increase If a customer adds another 5,000 developers, then we may see some ups and downs in the scalability aspect of this tool, but we are all good with the scalability and stability so far.

    How are customer service and support?

    I haven't interacted with the support team because things are working well and we've never had issues with the platform. 

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

    We used open-source Git and later used GitLab, which is a flavor of Git. GitHub, GitLab, Bitbucket, and Azure Repos are all flavors of Git. The underlying version-control functionalities come from Git, but different vendors have their own flavors. I have experience in all four of these, which are Git.

    How was the initial setup?

    I wasn't involved in the initial installation, but I installed the open-source flavor of Git, which was straightforward. Enabling the AD or LDAP is the most important thing in the enterprise setup. I have not looked into that because the customer enabled it. I never got a chance to integrate LDAP with the access management system within GitHub.

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

    It's a GAT now. We are using the enterprise edition. I don't use open-source any longer. I have no clue because it's all owned by the customer. We are only consultants in the project, right? So we don't have access to those details.

    What other advice do I have?

    I rate GitHub 10 out of 10. If you are using GitHub, your development team should define the branching strategy. One popular solution is Gitflow. There are different branching strategies available. You can use the main branch loan and a toggling feature development approach where one branch is sufficient. 

    However, people with parallel releases need a parallel development strategy, where multiple branches will come into play. You should consider which branching strategies apply to your current industry and development strategy. Pick one of them, learn, and adopt it in your project.

    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
    PeerSpot user
    Project lead at a tech services company with 10,001+ employees
    Real User
    Top 20
    Easily accessible but requires some technical knowledge
    Pros and Cons
    • "A great feature is being able to have different repositories and different kinds of projects in a single solution at a single time. It's just a click away."
    • "The only thing I see missing in GitHub is that it isn't very user friendly for key personnel who don't have in-depth, technical knowledge. In Jira, there are many functions to upload our test cases, and in GitHub we can only do it manually. There are functions which can be used to upload different files, but that still requires some technical knowledge. A layman cannot do it."

    What is our primary use case?

    We use GitHub because we don't have any paid solutions, and GitHub is freeware. It's open to all, and there aren't big licensing fees, like with Jira or any other tool. Apart from that, because it's totally cloud based, we don't need any extensions, and our developers and DevOps are all in sync and are able to get help with their second branches. So, we are all using the same platform to manage our product.

    It's a cloud solution.

    How has it helped my organization?

    It is easily accessible. Even if someone doesn't have the paid version of the GitHub license, the minimum license, they can still use it for themselves. Sometimes Jira extensions are only installed on a server on the client side, so you need a VPN connection to access that, but with GitHub access is based on your ID, so you can access it from anywhere.

    While we are working from home because of the pandemic—and when we didn't have proper VPNs—it helped us assess all our defects, which are placed in GitHub very easily. We don't need to rush the VPN connection and then access all these things. It was really easy. It also has two-factor authentication, which helps us authenticate users very easily.

    What is most valuable?

    A great feature is being able to have different repositories and different kinds of projects in a single solution at a single time. It's just a click away. If I compare it with Jira, that's one of the best features.

    What needs improvement?

    The only thing I see missing in GitHub is that it isn't very user friendly for key personnel who don't have in-depth, technical knowledge. In Jira, there are many functions to upload our test cases, and in GitHub we can only do it manually. There are functions which can be used to upload different files, but that still requires some technical knowledge. A layman cannot do it. Someone has to be trained with all those artifacts.

    In the next release, I would like to see more QA friendly features like extensions. In Jira, you can modify different extensions. GitHub doesn't have that. They have many standard features, but sometimes I feel that there is something that I need but it's missing.

    For how long have I used the solution?

    I've been using GitHub for more than three years.

    What do I think about the stability of the solution?

    GitHub is very stable. I have seen many different sections which are also easily accessible. For developing a product, you don't need to travel or do research work. In GitHub, there are many other repositories that are public. You can also navigate and see what others are doing if they have some public examples. It's like a type of overflow. You get many examples from this, and then by seeing those examples, you can directly implement that work and have a glimpse at other things.

    What do I think about the scalability of the solution?

    Scaling the solution is very easy. 

    In my organization, there are 130 people currently using GitHub. It has been used quite extensively because 130 guys are using it on a daily basis for checking their codes along with user stories.

    We haven't needed anyone for maintenance of this solution.

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

    I have previously used Jira. When I was using Jira, I wasn't applying projects, so they were funding the project and using the Jira platform for managing their product. Currently in the project I'm on, we don't have a lot of funds for Jira, so we searched for the open source and found GitHub. We liked it because it was solving all of our queries. Whatever our needs were, we were able to accomplish them with GitHub.

    How was the initial setup?

    Initial setup was very simple.

    What about the implementation team?

    There was no implementation strategy because GitHub is cloud based. It doesn't require any sort of deployment from our end. There was just a configuration that we needed to do to make it work with our code. There were simple sections which we needed to run, but our developers were able to collaborate easily.

    We worked with our in-house team. There was no mediator between us.

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

    If there are only 10 people using a particular repository, then GitHub is free. But if we increase the number of users, we need to pay the normal charge for GitHub.

    What other advice do I have?

    I would rate this solution 7 out of 10. 

    If someone is managing the product as well as doing the test management, they should go with GitHub. It's very easy to understand and track everything, and you can even see the different check-ins. 

    If someone is specifically going for a test management tool and they need the proper agile-based tools, they should go for Jira.

    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.
    PeerSpot user
    Buyer's Guide
    GitHub
    November 2022
    Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    657,849 professionals have used our research since 2012.
    Vice President at a financial services firm with 10,001+ employees
    Real User
    Top 5
    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.
    PeerSpot user
    Mohan_S - PeerSpot reviewer
    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.
    PeerSpot user
    Ali Albousaifi - PeerSpot reviewer
    Information Technology Consultant @ CIM at a tech services company with 11-50 employees
    Real User
    Top 5
    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.
    PeerSpot user
    Michael Barlow - PeerSpot reviewer
    Chief Web Application Architect at Dbitpro, llc
    Real User
    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.
    Flag as inappropriate
    PeerSpot user
    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.
    PeerSpot user
    Moses NYOTA - PeerSpot reviewer
    Senior Software and Cloud Engineer at Velocis Technologies LLC
    Real User
    Top 5Leaderboard
    Easy to use, low learning curve, and is great for team collaboration
    Pros and Cons
    • "The learning curve is small."
    • "The solution needs some more controls for deleting code."

    What is our primary use case?

    We primarily use the solution for version control.

    What is most valuable?

    What I like about GitHub is the ease with which we can use it. For example, when you're developing an application that does not like compiling or does not require compiling, for example, PHP application and Python application. We need to update them on the client side. Sometimes we do automate using GitHub. We use it in a way that we can use it as an update tool on the client side so that when we make an update on the system on our side, it automatically pulls on the client side.

    The ability to work as a team is great. In the world of software development teams, like controlling code versions, it's very important to stay on top of everything. GitHub helps us a lot in that. In a distributed work environment where I'm coding here, somebody in India is coding a different part on the same application. We can coordinate very easily on GitHub and synchronize our code.

    It’s easy to set up.

    The learning curve is small.

    The stability is good.

    What needs improvement?

    The solution needs some more controls for deleting code and margin. Some of the challenges faced by developers are when maybe you have a junior developer who comes and maybe does something crazy on the repositories. More fine-grained control is required.

    For how long have I used the solution?

    I created my GitHub account in 2013. On serious developments, I started around 2017. That's when I went deeper into using it on a day-to-day basis in teams for coordinating the development of various applications.

    What do I think about the stability of the solution?

    It’s quite stable. there are no bugs or glitches. It doesn’t crash or freeze.

    When we are coding and see some unsafe code on the repository, GitHub is able to automatically scan and tell us, "You have a vulnerability somewhere. Maybe certain dependency you are using has vulnerability." And we can cut such vulnerabilities before we release the software.

    How are customer service and support?

    I've never contacted tech support for GitHub. We have not come across issues. Some of the challenges we get, we can sort as a team. If I'm in Kenya, somebody in India or the US might have the knowledge to solve such a problem and I can rely on them. 

    I haven't had a challenge that required me to contact tech support.

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

    We used Bitbucket for version control.

    We used TortoiseSVN for a short while for version control for one project. It’s a good one also.

    How was the initial setup?

    It’s very straightforward to set up. It’s not complex at all.

    The learning curve for GitHub is pretty small. The more advanced commands will take a bit of time to learn. However, the basic commands are easy to learn. In a few days, you're good to go.

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

    If you are using public repositories, basically, it's free. For private repositories, you have licenses. For now, we haven't taken any license for our ends, as most of our repositories are public. If we are doing an in-house development, we don't need a license.

    What other advice do I have?

    I’m using the latest version of the solution.

    I’d recommend the solution. It’s ideal for teams.

    I would rate it eight out of ten. It’s good. However, there is still room for improvement.

    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
    PeerSpot user
    Buyer's Guide
    Download our free GitHub Report and get advice and tips from experienced pros sharing their opinions.
    Updated: November 2022
    Buyer's Guide
    Download our free GitHub Report and get advice and tips from experienced pros sharing their opinions.