GitHub Reviews

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. 

We use GitHub whenever there is an infrastructure level deployment on any of the cloud platforms.

This solution is very easy to use which I like about it. The capacity to own artifacts and share them with others is another good feature. You don't have to write all your code from scratch, you can use available templates and alter the code according to your needs.

The initial setup and implementation could be easier, I had some difficulties with it at first but I don't have a development background.

I've been using this solution for around one year. 

The solution is pretty stable and straightforward, but having experience helps.

I found this product to be scalable, we have at least 500 to 600 users within our company. For a small-scale deployment two people are more than sufficient, but that would increase with the complexity of the deployment.

Any issues have been resolved by our own team, but I can say that Microsoft customer support is usually satisfactory.

The initial deployment was straightforward and took three to four months.

I would rate this solution an eight out of ten.

We are actually working with MuleSoft, and for that, we have to build our application. We are working for a company offering hotels and resorts. We are using GitHub for that process. We're building applications on it. 

It's good for branching and keeping the code. Overall, it is a good tool. We can find stable branches there and it is very easy to manage code there.

The interface is good.

We have found that it does allow for helpful integrations. 

It is really simple to set up.

They need to make it possible to recover branches. For any of the branch that does not have PR, that is unrecovered. So there should be an option to recover those branches.

I cannot recall coming across any missing features. 

The user interface on GitLab is better.

I've been using the solution for six or seven months. 

The solution is stable. There are no bugs or glitches. The performance is reliable. It doesn't crash or freeze. 

We have 70 to 80 users on the product currently. We use it on a daily basis.

It's very easy to scale as needed. 

I've never directly contacted technical support. As a developer, I'm not the one who would be contacting technical support. If there were issues, someone else in the company would deal with them. 

I previously worked with GitLab. They are pretty much the same. GitLab does have a very good user interface. That's the main difference.

The initial setup is simple and straightforward. it is not overly complex or difficult. 

As it is a solution that is on the cloud, there is no manual maintenance required. 

We do have a separate team that handles deployment. I don't handle deployments directly myself. 

I don't deal with licensing. I cannot speak to the exact pricing. 

I'm just a customer and an end-user. 

We currently work with the latest updates of the product. 

I'm a developer and I don't work with managing everything on GitHub. I just use it for putting in the code and merging branches.

GitHub actually is a pretty easy tool. It is not very difficult to understand. It is very easy. Everyone can set up branches there or work on it.

I'd rate it eight out of ten. If we could recover branches, I'd give it a perfect ten. 

Because Github is hosted in the cloud, we do not require many resources to maintain it. 

The security for this solution could be tightened up and improved. 

We have used this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

We have not needed to contact their support team frequently. 

The initial setup was straightforward. 

The licensing offered is on an annual basis. 

During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently. How useful these features are, depends on each business. 

I would rate this solution an eight out of ten. 

We use GitHub because we don't have any paid solutions, and GitHub is freeware. It's open to all, and there aren't big licensing fees, like with Jira or any other tool. Apart from that, because it's totally cloud based, we don't need any extensions, and our developers and DevOps are all in sync and are able to get help with their second branches. So, we are all using the same platform to manage our product.

It's a cloud solution.

It is easily accessible. Even if someone doesn't have the paid version of the GitHub license, the minimum license, they can still use it for themselves. Sometimes Jira extensions are only installed on a server on the client side, so you need a VPN connection to access that, but with GitHub access is based on your ID, so you can access it from anywhere.

While we are working from home because of the pandemic—and when we didn't have proper VPNs—it helped us assess all our defects, which are placed in GitHub very easily. We don't need to rush the VPN connection and then access all these things. It was really easy. It also has two-factor authentication, which helps us authenticate users very easily.

A great feature is being able to have different repositories and different kinds of projects in a single solution at a single time. It's just a click away. If I compare it with Jira, that's one of the best features.

The only thing I see missing in GitHub is that it isn't very user friendly for key personnel who don't have in-depth, technical knowledge. In Jira, there are many functions to upload our test cases, and in GitHub we can only do it manually. There are functions which can be used to upload different files, but that still requires some technical knowledge. A layman cannot do it. Someone has to be trained with all those artifacts.

In the next release, I would like to see more QA friendly features like extensions. In Jira, you can modify different extensions. GitHub doesn't have that. They have many standard features, but sometimes I feel that there is something that I need but it's missing.

I've been using GitHub for more than three years.

GitHub is very stable. I have seen many different sections which are also easily accessible. For developing a product, you don't need to travel or do research work. In GitHub, there are many other repositories that are public. You can also navigate and see what others are doing if they have some public examples. It's like a type of overflow. You get many examples from this, and then by seeing those examples, you can directly implement that work and have a glimpse at other things.

Scaling the solution is very easy. 

In my organization, there are 130 people currently using GitHub. It has been used quite extensively because 130 guys are using it on a daily basis for checking their codes along with user stories.

We haven't needed anyone for maintenance of this solution.

I have previously used Jira. When I was using Jira, I wasn't applying projects, so they were funding the project and using the Jira platform for managing their product. Currently in the project I'm on, we don't have a lot of funds for Jira, so we searched for the open source and found GitHub. We liked it because it was solving all of our queries. Whatever our needs were, we were able to accomplish them with GitHub.

Initial setup was very simple.

There was no implementation strategy because GitHub is cloud based. It doesn't require any sort of deployment from our end. There was just a configuration that we needed to do to make it work with our code. There were simple sections which we needed to run, but our developers were able to collaborate easily.

We worked with our in-house team. There was no mediator between us.

If there are only 10 people using a particular repository, then GitHub is free. But if we increase the number of users, we need to pay the normal charge for GitHub.

I would rate this solution 7 out of 10. 

If someone is managing the product as well as doing the test management, they should go with GitHub. It's very easy to understand and track everything, and you can even see the different check-ins. 

If someone is specifically going for a test management tool and they need the proper agile-based tools, they should go for Jira.