GitHub Reviews

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.

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.

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.

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.

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

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.

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.

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.

Initial setup was very simple.

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.

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.

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.

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.

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. 

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

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.

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. 

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.  

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. 

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

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.

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

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.

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.

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

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.

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. 

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.

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.

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

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.

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.

I have been using GitHub for three years.

This solution is quite stable.

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

We very seldom need support.

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.

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

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.

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.

We use GitHub for AI features.

GitHub is a cost-effective solution. The solution provides good customization and support.

I have been using GitHub for a couple of years.

We haven’t faced any stability issues with GitHub.

The solution’s initial setup is straightforward.

GitHub is a cost-effective solution.

GitHub's branch protection feature is effective in our workflow management. I work with the cloud version of GitHub. The documentation is enough to resolve issues with the solution. People working with Microsoft tech can use GitHub. Microsoft is investing heavily in this tool. Using GitHub depends on users' use cases and their technologies.

Overall, I rate the solution an eight out of ten.

We used the product for CI/CD.

I like the CI/CD features. The tool was easy for me to use because I had used it for a long time. GitHub is a leader in the domain. Others copy GitHub.

The stability can be improved.

I have used the solution for 15 years.

I rate the tool’s stability a ten out of ten. The vendor modifies many things and provides new releases regularly.

The tool is very scalable and reliable. There is no loss in quality.

It is easy to set up the account and give permissions to others.

The product can be deployed in-house.

The product is reasonably priced.

I have also used GitLab. There is not much difference between GitLab and GitHub.

I used GitHub in my previous organization. In my current organization, we mostly use Azure. GitHub is easy to use and easy to manage. It's good for integration and for multi-worker projects. It is robust. Overall, I rate the solution a nine out of ten.

I'm mostly using the solution for the backup repository. We are also using it for bug tracking and Scrum management.

I like to do projects using the tool. I also like the check-in and check-out features. The product helps our team collaborate across different locations.

The merging features can be improved. The tool has plugins that allow CI/CD integration. It would be helpful if it were available out of the box.

I have been using the solution for almost ten years.

The product is very stable. I rate the stability a ten out of ten.

The product is scalable. We had 100 users initially. Now, we have reduced it to 50. The solution is used daily in our organization. The usage will increase as our company grows.

I used SVN before. I switched to GitHub due to SVN’s cost.

I will recommend the tool to others. If someone is looking for a repository backup solution, they can use GitHub. It helps with task management. It is helpful in AI development projects. It is a valuable product. It does justice to the price. Overall, I rate the solution an eight out of ten.

I use the solution as a repository to store the source codes that I create with small tools. I also use it to share codes with customers when it is impossible to directly upload them from my computer to the customer’s environment due to some network restrictions. However, it is possible to download from GitHub in such environments. So, I transfer my source codes through GitHub so that they can download and implement them.

GitHub is a simple repository of source codes. The ease of use is valuable. It supports collaboration within the team very well.

We face issues with synchronization while working with teams. It is difficult to synchronize the source code between team members.

I have been using the solution for more than five years.

The tool is very stable. I do not face any unavailability.

I use the solution for my personal use cases.

The setup is very easy. It is very easy to create a new repository for a new project. It is easy to create teams.

The tool is of great value. It provides space for source codes for future use. If I migrate from one computer to another, I can still use the same Git without any complications.

We must pay the licensing fee if we want to use the tool commercially.

I do not use any pipelines or other tools. I do not use the tool frequently. I mostly develop things on my computer and hand them over to the customers. People must start using the product. It is easy for users who have experience with other Git tools like GitLab or GitBucket. We just have to create a project and clone it. Overall, I rate the product a nine out of ten.