GitHub Reviews

I use Github to store the code that I write. I don't use it very much. It may be used more by the active developers.

I am using it, it was easy to set up and it is working well for me.

I would want to see some form of code security scanning implemented.

Our company has used GitHub for a long time. I have been using this solution for two and a half years.

We use GitLab release 14.6.7.

I did not have any issues with the stability of Github. It worked seamlessly.

I have not contacted technical support.

Some of these tools are associated with our parent company. We consume them. I believe they were set up by our parent company's tools team.

The initial setup is straightforward.

Client setup takes about 15 to 15 minutes on the workstation where I do my development.

I completed it myself using the documents provided, and I was able to connect it by following the steps.

I would rate GitHub a nine out of ten.

I use GitHub for development, including version control and container services.

With GitHub, we can manage our development progress, CID, and continuous integration. It helps streamline our development processes effectively.

I really like the functions that GitHub offers. The features are very helpful for my needs.

There could be some improvements related to the automation of certain processes, especially with the integration of artificial intelligence. This would make some tasks more efficient.

I have been working with GitHub for more than one year.

I would rate the stability of GitHub as nine out of ten. It is very stable for our needs.

For scalability, I would rate GitHub nine out of ten. It scales well with our requirements.

The setup process for GitHub was straightforward and not complex.

If you are a start-up or a small company with a few projects, GitHub could be expensive because of the management costs.

GitHub is essentially a repository of code. It's where you source your code with the client and allows you to use Git. You get versioning and everything else for multiple deployments or codes. That's how we use it.

We stopped the development code on our machines, and we moved everything to GitHub. So, everyone is working on the latest code no matter what we do.

The accessibility is free.

There is room for improvement in terms of interface because  I had a problem with developers who didn't know what GitHub was, and it was a little bit strange to explain. 

I have been using GitHub for three years. We use the latest version. 

I would rate the stability a ten out of ten.

The scalability is very good. It has never let me down.

The initial setup is okay. You need to know what you're doing.

I saw 100% ROI. 

Price is free. 

It is way better than developing software by yourself. I would definitely recommend using the solution.

Overall, I would rate the solution a ten out of ten.

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 are using GitHub for the development environment. After we develop some applications, we are pushing actually on both settings. 

I would like to see more security where a plugin was available for us to update in relation to security.

I have been using GitHub for the past seven years.

We are finding GitHub is very stable. Because it is the one that we are actually using on the cloud, it is easy for actual resources.

We currently did not choose the option with the subscription, but the free version actually provided by GitHub and GitLab is acceptable for us. Maybe the institution wants to increase the number of developers to twenty from what we currently have three, then definitely we will increase and prefer to have additional services from GitHub as well as GitLab.

Technical support is excellent on a scale of one to ten I give technical support a ten.

Positive

The initial setup is straightforward and easy. For someone who has actually good experience in software development, including using a repository solution, I think it is easy. Beginners need to refer to the manual and see some online tutorials to receive assistance so that it is easier for them to setup.

You can do the deployment in-house without a problem.

We are currently paying nothing for GitHub.

I think I remember Tortu was the name of the product. There is a Q Balance in our repository providers. I think that one is Microsoft. I do not know exactly, but we are not using it. We tried it but we returned to GitHub.

If you are working in development I would recommend using GitHub. I would rate GitHub a ten 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.

We use this solution to manage and store our development work.

This product allows us to easily collaborate on development tasks with our subcontractors, and control the workflow as the project progresses.

We would like this solution to have a more user-friendly interface.

We have been working with this solution for two years.

We have not encountered any issues with the stability of this solution.

We have found this to be an easily scalable solution.

The initial setup for this solution was very straightforward.

We also evaluated Microsoft TSS.

I would rate this solution an eight out of ten.

We use GitHub to share the source code and can give users different permissions to use different parts of the project. Whenever a developer changes a source code, it can push it easily, and others can see the change and who made it.

It is a very good solution. GitHub allows the backup of our source code. So we are sure that if all the computers in our company crash and the hardware fails, we can access our code on GitHub. Also, in the past, every repository we built was publicly available to anyone, and others could see our source code, but now we can make a private repository and share it with our team. This feature is very valuable and good for us.

It is very tricky to work with GitHub. For example, it is difficult to merge a code or restore it to an older version. It would be great if they provided a tool that merges the code better and more intelligently.

We have been using this solution for ten years.

It is very stable. Whenever it is connected, it always works, and we love it.

It is scalable. We can easily extend to team members, with a team of about six or seven people in a GitHub repository. Most users are developers, but we can also provide viewing access to others. We don't have any distinct plans to increase our usage of GitHub.

We have not used technical support because GitHub has a large community of users, so if there is an issue, we can find the solution on Google.

We did not use any other solutions before GitHub.

The initial setup was very easy.

It is a free solution. 

I rate this solution a ten out of ten. I recommend GitHub to others to back up their source code or share it among different people on the same project. GitHub is integrated very well with Microsoft Visual Studio and .NET. For example, if we make a project inbox for Visual Studio, we can push the code to GitHub by adding our account to Visual Studio.