GitHub Reviews

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 primarily use the solution for sourcing candidates.

I like finding individuals with more repositories and more followers, et cetera. It’s great to find the talent who is available and has particular skills.

The solution is scalable.

I do not think they have to increase storage. There’s enough.

From the recruiting standpoint, I would like to see email IDs and phone numbers and a brief introduction about their profile.

I’ve been using the solution for about a year.

The solution is very scalable. It’s expandable if you need it to be.

I’m not sure how many people use the solution in our company.

I’ve never used technical support in the past. I can’t speak to how helpful or responsive they would be.

Positive

We did not previously use a different solution.

There isn’t really an initial setup to deal with.

I can’t speak to the exact cost of the solution.

I’m a customer and end-user.

I’d rate the solution eight 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. 

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.

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 are using GitHub for all of our repositories. We can store the code, collaborate with different developers, build, and create a pipeline.

GitHub storage is one of the main requirements and it could improve.

I have been using GitHub for approximately four years.

I have found GitHub stable.

GitHub is scalable.

Every developer in the R&D department is using GitHub in my company. There are approximately 2,300 people in the R&D department.

I have not contacted technical support to need to contact support.

We used different solutions prior to GitHub, such as Perforce and Rational.

The licensing model for GitHub is user-based. Whenever the new developer joins we have to get a new license and register their ID. The overall price of the solution is reasonable.

I would recommend the solution to others. It is very good.

I rate GitHub a nine 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. 

I use the solution to store most of my Python projects.

This product is very good for storing and versioning code.

The UI is a little outdated, so that could be improved. 

I have been using GitHub for six months.

The stability of the solution is sufficient.

The solution doesn't need to be scaled in this case, as it's just for my personal use.

I have never had to contact technical support. 

There was no need for an initial setup as I just use the solution on the cloud. 

I haven't had to pay anything for GitHub, I use the free version. 

I rate this solution an eight out of ten, and would recommend it to other users.