GitHub Reviews

We are customers of GitHub.

GitHub provides the SFH key to protect our passwords and our connection, it's a helpful product. It secures our repositories so any attempt to access from outside the company is blocked. We also have control of our product versions in GitHub, which is very useful. I like the fact that you can use it on any device.

The only problem we have is that our firewall was blocking cloning and downloading with SSH.

I've been using this solution for three years.

GitHub is stable. In the three years that I've been working with it, we've had very few problems.

Stability is good, we have around 200 users.

I never use the technical support of GitHub. I believe it's user-friendly but I've never needed to access it.

This is a free solution so there are no licensing costs.

I rate this solution 10 out of 10.

We use this solution when we speak about the storage, sizing requirements, and POCs.

GitHub is pure or open-source; you can access it anywhere. You can have a lot of collateral information. You can make the changes and do the reviews from one place. 

I think it would be valuable to have more security. Some of the data is very open to everyone.

I have been working with GitHub for three and a half to four years.

It is a stable solution. However, the market is always growing

It is scalable. Most companies and big organizations have a repository on the top scale.

They are very quick.

It is pretty straightforward. You just use your login ID and credentials.

You do not require any third party to configure it for you.

I would rate GitHub an eight and a half out of ten.

We are using GitHub for all of our repositories. We can store the code, collaborate with different developers, build, and create a pipeline.

GitHub storage is one of the main requirements and it could improve.

I have been using GitHub for approximately four years.

I have found GitHub stable.

GitHub is scalable.

Every developer in the R&D department is using GitHub in my company. There are approximately 2,300 people in the R&D department.

I have not contacted technical support to need to contact support.

We used different solutions prior to GitHub, such as Perforce and Rational.

The licensing model for GitHub is user-based. Whenever the new developer joins we have to get a new license and register their ID. The overall price of the solution is reasonable.

I would recommend the solution to others. It is very good.

I rate GitHub a nine out of ten.

We use GitHub instead of our regular shared drive. It offers instant access to shared folders as well as good security.

The GitHub repository needs an upgraded user interface and overall UI improvements. In Automation Anywhere, we have one repository where you can download or upload information. They have two interfaces in a single view that has verification. It would be good if Github offered the same. 

I have been using this solution for five years. 

This solution is somewhat stable, but requires additional supporting products.

This is a scalable solution. We have more than 2,000 users.

I would rate this solution a seven out of ten. 

I use the solution to store most of my Python projects.

This product is very good for storing and versioning code.

The UI is a little outdated, so that could be improved. 

I have been using GitHub for six months.

The stability of the solution is sufficient.

The solution doesn't need to be scaled in this case, as it's just for my personal use.

I have never had to contact technical support. 

There was no need for an initial setup as I just use the solution on the cloud. 

I haven't had to pay anything for GitHub, I use the free version. 

I rate this solution an eight out of ten, and would recommend it to other users. 

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. 

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. 

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.

The solution could have better support for the Markdown language.

I've been using the solution for over ten years, probably since its beginning. 

The solution is very stable, they have been working on it for over a decade. 

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.

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.

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.

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.

We have an enterprise licensing agreement, and I am not part of the finance department so I can't say how much it costs. 

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. 

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.

Because Github is hosted in the cloud, we do not require many resources to maintain it. 

The security for this solution could be tightened up and improved. 

We have used this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

We have not needed to contact their support team frequently. 

The initial setup was straightforward. 

The licensing offered is on an annual basis. 

During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently. How useful these features are, depends on each business. 

I would rate this solution an eight out of ten.