GitHub Reviews

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 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 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 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.

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. 

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 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. 

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.