GitHub Reviews

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

GitHub allows us the option to push files from a non-UA method or directly upload files from the UA. You can integrate GitHub with Jenkins to do CI/CD.

GitHub could add some more security features. 

We've been using GitHub for a year. One of our clients advised us to switch to GitHub, so we did. 

GitHub is stable. I haven't had any issues so far. 

We have the option to add storage if needed, so it's scalable. 

We've never contacted GitHub support. If we have a technical issue, I'll usually search for answers online. It's the same with other data tools like Postman. 

GitHub doesn't require any setup. You only need to create an account and a repository. After that, you start adding your files. 

I rate GitHub 10 out of 10. I only use it for storage, so I don't have any problems with it. If you're looking for storing files and code, GitHub is the best and most secure solution. 

The solution mainly serves as our project repository. We use it to maintain different environments with the help of branches.

The product has a good UI. It's simple and easy to access, and technical help is easily available. The two-factor authentication security is another valuable feature. 

I would like a more graphical, user-friendly UI, to avoid writing so much code on cmd.

For personal use, I've been using the solution for two or three years. But in my office, we started using it this year.

Stability is good, it's stable. I haven't found any issues to date, even though it's big data. It works well.

It's a scalable solution. 

We have an infrastructure team that handles technical support and everything else. The things we need are easily available on the internet.

Positive

We used to use GitLab (the free version I think), which had frequent deployment issues. So that's why we shifted to GitHub.

My organization installed everything, including the two-factor authentication security. 

We implemented the solution in-house.

I would rate the solution nine out of ten.

Syed:
So, basically, I can store my code in some repository, so we can manage also that version control. So, if he developed some applications, so we can manage with versions, so that feature GitHub provide, so we can create some repositories. Through repositories, we can manage the versions, so it's very useful. So, also and that GitHub provide some CI/CD pipeline feature, so we can integrate CI/CD through GitHub, so whenever I commit that code, it will automatically deployed in our servers, so it was a very useful feature in GitHub.

Tutorial videos within the GitHub dashboard will very helpful.

I have been using this solution for one year. 

This is a stable solution. 

This is a scalable solution. We have between 300 to 400 users. There are five DevOps staff in our team who take care of maintenance.

This is an open source solution and does not include licensing. 

I would rate this solution a nine out of ten.