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.

I am a senior product development engineer and I use GitHub in this capacity.

Essentially, this is the Git product, but in the cloud.

The most valuable feature is the fact that it's cloud-based, and we don't have to manage an on-premises server to use it.

It would be better if the amount of storage were increased.

We have been using GitHub for between six and twelve months.

GitHub is a stable solution.

This is a scalable, cloud-based product. We have a small team and do not plan to increase the number of users.

We have never needed to contact technical support. Any problems that we have had, we have always been able to solve.

I would rate the technical support a two or three out of five.

Neutral

I have used on-premises repositories but it was a long time ago.

No installation is required.

There are no licensing fees for the features that we use. We are on the free tier.

This is a product that I recommend for developers because everybody in the software development field is using it.

I would rate this solution an eight out of ten.

We use GitHub for source control.

GitHub is convenient and easy to use.

GitHub should provide more integration in their next release, including integrating with Jenkins, CI/CD and Jira.

We have been using GitHub for two years.

GitHub is a stable solution.

The solution is scalable. We have approximately 200 users.

Prior to using GitHub, we used Subversion, or SVN and CVS. We switched to GitHub because of the cloud enablement as well as the ease of use.

I would recommend GitHub to anyone considering implementing the solution into their organization. 

Overall, I would rate GitHub a nine out of 10.

We are actually working with MuleSoft, and for that, we have to build our application. We are working for a company offering hotels and resorts. We are using GitHub for that process. We're building applications on it. 

It's good for branching and keeping the code. Overall, it is a good tool. We can find stable branches there and it is very easy to manage code there.

The interface is good.

We have found that it does allow for helpful integrations. 

It is really simple to set up.

They need to make it possible to recover branches. For any of the branch that does not have PR, that is unrecovered. So there should be an option to recover those branches.

I cannot recall coming across any missing features. 

The user interface on GitLab is better.

I've been using the solution for six or seven months. 

The solution is stable. There are no bugs or glitches. The performance is reliable. It doesn't crash or freeze. 

We have 70 to 80 users on the product currently. We use it on a daily basis.

It's very easy to scale as needed. 

I've never directly contacted technical support. As a developer, I'm not the one who would be contacting technical support. If there were issues, someone else in the company would deal with them. 

I previously worked with GitLab. They are pretty much the same. GitLab does have a very good user interface. That's the main difference.

The initial setup is simple and straightforward. it is not overly complex or difficult. 

As it is a solution that is on the cloud, there is no manual maintenance required. 

We do have a separate team that handles deployment. I don't handle deployments directly myself. 

I don't deal with licensing. I cannot speak to the exact pricing. 

I'm just a customer and an end-user. 

We currently work with the latest updates of the product. 

I'm a developer and I don't work with managing everything on GitHub. I just use it for putting in the code and merging branches.

GitHub actually is a pretty easy tool. It is not very difficult to understand. It is very easy. Everyone can set up branches there or work on it.

I'd rate it eight out of ten. If we could recover branches, I'd give it a perfect ten. 

It's a code repository, so it is used for checking it, code, and version control.

This solution is deployed on the cloud. 

There are 10-15 people using this solution in my organization.

The most important feature of GitHub is the maintainability of the versions of the code. It allows multiple people to work on the same use case, so anyone can check in and check out, and that history is available.

We are not able to access GitHub from our VPN. Whereas on the customer side, we are able to access the open source data. If the data was more accessible in my company as well, I think it would be useful to have the ability to work with VPN.

I would also like to see deeper integration with Microsoft products.

It's a stable solution.

It's scalable.

It's a simple process.

I think Microsoft SVN is also a good solution compared to GitHub. Our organization is tied up with Azure, and many of the Microsoft tools like Office or 365 are provided. It's easy to have Microsoft for the code repository as well rather than getting GitHub.

Using the microsoft.net framework is easier than using UiPath on .NET.

I would rate this solution 8 out of 10.

We just use GitHub for the repository in our company.

So we have a central repository. So, we do recommend the need to push and pull everything, and that's how we use it.

The requests, push, pull, merge, and everything else in the solution are its valuable features. Later, people make their changes.

I don't have any comments on the improvement needed in the tool since I'm okay with it. I don't have anything really in mind. It's not like I am picky, and I don't need to be picky unless it's really an overblown, like, there are some bugs or some glitches or something like that in the solution. As of now, everything looks fine.

Scalability is an area with a shortcoming, because of which it has room for improvement.

I have been using GitHub for more than five years. We just use the solution for work in our company.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

We plan to increase the usage of the solution. There are a lot of products out there in the market, but I wouldn't say I would recommend it, but if you use it, then it's fine. I don't really compare much as long as that's what is expected from the solution functionality-wise is fulfilled. So, then I am fine with it.

I don't use the solution's customer support.

Regarding the initial setup, I rate it an eight on a scale of one to ten, where one is difficult and ten is easy.

The solution is deployed on a private cloud since it is a corporate thing. We don't go for a public cloud.

The deployment is fast since we just have to run the script, and once it's done, it takes a few minutes.

My company has schedules, and we assign people to do the deployment. So, it's rotational. Let's say I do the deployment this week, and then another person does it next week.

I don't know about the solution's cost. My company purchased it. Before, we used to receive the free version, but then they purchased some of the features.

I am using the solution, and I am fine with it. I would definitely recommend the solution to those planning to use it. I rate the overall solution an eight out of ten.

We used it mainly for version control and when we wanted to test an application at the initial stage or launch the mock-up version.

When it comes to version control, GitHub is fulfilling all that requirements. GitHub is the best tool for source repositories.

You can create public and private repositories.

GitHub could expand the limits of the free version. People are waiting for CNS. 

I have been working with Github for the past eight years.

I consider it stable as of now.

It is also scalable with respect to the branches.

We have not had to use technical support. The documentation that was provided for troubleshooting worked effectively.

The setup was very straightforward and easy for me.

We did not compare GitHub with other options.

I would rate GitHub a nine out of ten.