GitHub Reviews

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. 

GitHub is mainly used for code control. We have three environments, and we keep their codes as per those environments. As and when required, we clear pull requests as well. The main purpose of GitHub is to keep our code available.

GitHub is simple to use and has great performance. Even if I'm not in the office, I can access and work on my code from anywhere with my account credentials. GitHub has an interactive user interface.

The solution should have less integration with the AI part, but it needs to add features with other automation tools so that it can be easily integrated.

I have been using GitHub for five and a half years.

Around 200 users are using GitHub in our organization.

The solution’s initial setup is straightforward.

If I go as per the process we follow, it will take hardly half an hour for me to deploy the solution.

You don't have to pay for a license if you are using the free version. It gives you all the possible features it has.

GitHub is deployed on the cloud in our organization. Users who have to manage their code can create a GitHub account and start using it.

Overall, I rate GitHub ten 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.

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 primarily use the solution for version control.

What I like about GitHub is the ease with which we can use it. For example, when you're developing an application that does not like compiling or does not require compiling, for example, PHP application and Python application. We need to update them on the client side. Sometimes we do automate using GitHub. We use it in a way that we can use it as an update tool on the client side so that when we make an update on the system on our side, it automatically pulls on the client side.

The ability to work as a team is great. In the world of software development teams, like controlling code versions, it's very important to stay on top of everything. GitHub helps us a lot in that. In a distributed work environment where I'm coding here, somebody in India is coding a different part on the same application. We can coordinate very easily on GitHub and synchronize our code.

It’s easy to set up.

The learning curve is small.

The stability is good.

The solution needs some more controls for deleting code and margin. Some of the challenges faced by developers are when maybe you have a junior developer who comes and maybe does something crazy on the repositories. More fine-grained control is required.

I created my GitHub account in 2013. On serious developments, I started around 2017. That's when I went deeper into using it on a day-to-day basis in teams for coordinating the development of various applications.

It’s quite stable. there are no bugs or glitches. It doesn’t crash or freeze.

When we are coding and see some unsafe code on the repository, GitHub is able to automatically scan and tell us, "You have a vulnerability somewhere. Maybe certain dependency you are using has vulnerability." And we can cut such vulnerabilities before we release the software.

I've never contacted tech support for GitHub. We have not come across issues. Some of the challenges we get, we can sort as a team. If I'm in Kenya, somebody in India or the US might have the knowledge to solve such a problem and I can rely on them. 

I haven't had a challenge that required me to contact tech support.

We used Bitbucket for version control.

We used TortoiseSVN for a short while for version control for one project. It’s a good one also.

It’s very straightforward to set up. It’s not complex at all.

The learning curve for GitHub is pretty small. The more advanced commands will take a bit of time to learn. However, the basic commands are easy to learn. In a few days, you're good to go.

If you are using public repositories, basically, it's free. For private repositories, you have licenses. For now, we haven't taken any license for our ends, as most of our repositories are public. If we are doing an in-house development, we don't need a license.

I’m using the latest version of the solution.

I’d recommend the solution. It’s ideal for teams.

I would rate it eight out of ten. It’s good. However, there is still room for improvement.