GitHub Reviews

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. 

We use this solution to exchange files and manage version control.

GitHub have a built-in software application development environment and this has been most useful. 

The storage for this solution could be improved. 

I have been using this solution for two years. 

This is a stable solution. 

This solution is potentially scalable. 

The technical support for this solution is good. 

Positive

The installation for this solution is very easy. 

I would recommend this solution to others. I would rate it a nine out of ten. 

We use Github to upload projects and share files. Github is used for personal application development and building plugins, Normally, we manipulate GitHub from the native system, so we upload the files to GitHub and get a URL. My company has more than 300 developers, and about half of them use GitHub for application storage and formatting applications.

GitHub is good for collaboration because everyone can access it or we can restrict access to a few users. If I upload a file and share the URL, it's not restricted to a set number of users. Everyone with the link can download the files.

GitHub could add more security features. I am not sure how secure it is. If they provide more security features, then it can be used in more official applications.

I have been using GitHub for the last five years.

I have never tried a large-scale upload on GitHub. I create separate folders for each application. Right now, I have 15 to 20 applications uploaded and haven't faced any limitations or storage issues so far.

It is a free platform we only use internally, not for official purposes.

I rate GitHub nine out of 10. We use it to manage plugins and everything else. Even though it is a coding platform, it's useful for any technology. I would recommend using GitHub as a base for configuration and coding activities. 

Once you upload something on GitHub, you can integrate it with your local repositories or other platforms. It has broad compatibility with other solutions, so you can use GitHub even if you have a different platform. 

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.

We use it to collaborate on projects, and store projects as well. 

This solution is just easy to use.

Github needs more storage.

I have been using this solution for about five years.

It is stable.

It is scalable for what we need.

There were other solutions that we used previously.

We are just on the entry tier; it is a free tier for education.

I would rate Github an eight out of ten.

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.

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.

GitHub is used to store my source code or raw reports.

The most valuable features are GitHub are the standard features, they are very useful.

GitHub could improve by being more user-friendly.

I have been using GitHub for approximately 15 years.

GitHub has high availability.

I have not used the support from GitHub.

I have not used another solution prior to GitHub.

I would recommend this solution to others.

I rate GitHub an eight out of ten.