GitHub Reviews

We use GitHub for code versioning; with multiple developers working on the same projects. It gives us a central source for our code. We commit our code to the cloud using the API called Gita, which tracks which developers have uploaded the code, which have changed it and so on. 

The code versioning is excellent, and having a detailed log, including every change made to the code by every developer, is invaluable. It makes it so that if there is a bug or problem in the product channel, we can find exactly where it happened and how to fix it.

There can be conflict issues when two developers work on the same file or line of code, and it would be great to see that improved, possibly with an AI solution. 

A great feature would be the AI for code conflicts, enabling us to choose which code edit is the one we want to go with. 

I've been using the solution for about eight years. 

GitHub is stable, and they are improving in terms of security. 

The product is scalable. We have about 20 end users in total. 

The support is average; they can be inconsistent and it would be good if they were more responsive. 

Neutral

The initial setup is a little complex because it requires some knowledge of GitHub and code versioning. Certain steps need to be taken in a specific order, and if any are skipped or done wrong, it can lead to failure. Aside from the mentioned challenges, one staff member can complete the setup.

There is sufficient documentation to help with the setup process.

The setup was implemented in-house. 

GitHub is an open-source product, but when using the free-to-use version, anyone can see the code we're working on.

If you purchase a license, there's an option to make your code private, and our organization has a license.

I would rate this solution a nine out of ten. 

Compared to the competition, I would say GitHub is the best, as it has the most robust security, and most of the developer community is familiar with it. Bitbucket is also an excellent solution with solid security, but more developers would require training.

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. 

GitHub is used to manage distributed versions of systems to allow developers using production operating systems to work without distributed dependency. It is a distributed version control system where we get the repository downloaded on our laptops and can work without any idle time.

Any complex banking can be handled very easily in GitHub. It allows us to integrate with tools like Grid, where we can merge and resolve conflicts without any hassle. 

This solution could be improved if migration was fully automated to make it easy, for example, to migrate repositories into GitHub. 

I have used this solution for eight years. 

The customer service for this solution is not great. The team either takes a long time to respond or doesn't respond at all. 

Neutral

I have previously used ClearCase and Submersion but have used GitHub for the past eight years. ClearCase is a centralized system but has expensive licenses and running processes within the system took a long time. This is the reason we moved to Github.

The initial setup is straightforward and only involved four to five steps. 

I would rate this solution a ten out of ten. 

We use GitHub for versioning and to provide a place on the cloud to store code so that people can work on it together.

The most valuable features are the Git Hooks and SSH keys.

The Projects Tab, which shows you the todo list and the progress for projects, is very helpful.

I would like to see integration with Slack such that all of the changes made in GitHub are reflected there. You would simply enter the Slack URL and the notifications about code changes would be forwarded.

We have been using GitHub for at least a year.

There were a few cases when we were unable to reach GitHub but for the most part, it is stable.

We have different people in the company who are working on different projects on GitHub. It is safe to say that we have about 50 people in total who are using the platform.

I have not been in contact with technical support. With respect to community support, I have noticed that it is pretty evolved. I have used it often and find that it is very useful.

We used to use BitBucket, but when Microsoft announced that private repositories would be free on GitHub, we switched.

The initial setup is super easy.

The private repositories are free, which is very good.

GitHub is definitely a platform that I recommend people use.

I would rate this solution a ten 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.

Our organization uses GitHub for version control.

GitHub allows you to create pages, if you want to share documents you can create articles and diagrams with GitHub and share.

On a personal level, GitHub assists you to create your own website.

GitHub uses basic configuration, but messaging is not clear. For example, when a database denies a username and password, it says "asking for person accepted".

I would like to see improvements with merging code from multiple branches. When more than one developer is working at the same time, it becomes complicated. It very much depends on the person doing the merging. There is no assistance from the tool itself. If a mistake is made, the tool will not be able to correct it. It would benefit from an automated checker.

I have been working with GitHub for five years.

The solution is stable.

GitHub is scalable. Our organization has 1,000 people. Approximately 80% would be using GitHub.

The initial setup of GitHub is very simple.

I would give GitHub a nine out of ten overall.

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.