GitHub Reviews

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.

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. 

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 this product to host the code base for different development teams within our organization and for versioning the codes and integrating with CI/CD tooling. We have a partnership with GitHub and I'm a product manager. 

Using GitHub has been beneficial for us because it was an easy process for users and it has improved efficiency. In contrast to Bitbucket or Azure Repos, moving things over to GitHub was simple.

We like the simplicity of GitHub and that it is free of complications, as opposed to other tools on the market. Its ability to be integrated with third-party softwares such as Azure Pipelines or Jenkins, is great.

The solution lacks sufficient support in terms of professional services that could be provided proactively to customers. The product documentation could be improved. What currently exists on the GitHub website is not complete and not sufficient to help end users with customizations or integrations, tools for code quality, or app security. In the next release, I would love to see something around security as well as some code analysis and open-source vulnerability detection features. It would be helpful if there was a better DevOps offering from GitHub. GitHub Actions is still maturing.

I've been using this solution for two years. 

The solution is stable. 

GitHub is scalable, we have around 120 users. They are mainly software developers and engineering managers. We have three people, DevOps engineers and support engineers, working with GitHub and we're likely to expand usage. 

Our technical support experience has been quite good in terms of response and expertise.

Positive

We previously used Bitbucket and Azure Repos. We switched to GitHub because of its ease of implementation and ease of onboarding new users, as well as its integration with third-party tooling.

The initial setup was straightforward. We are in a regulated industry with a large volume of organizations, and there are additional processes that need to be taken care of. Taking all that into account, the deployment took about 10 days. Implementation of GitHub alone just takes a few hours. We worked with a third-party vendor. 

The product certainly saves us a lot of time and that equals money. We save time in terms of how the code base can be managed and versioned. We have better control over the release of the product, and we have reduced the time that takes. We're getting a good ROI. 

I recommend this solution even though it does not provide the complete suite. There are DevOps services coming in from Microsoft, for example, and you need to go to GitHub Actions separately. Source code management is better on GitHub and I would rate that higher.

Overall, I rate this solution seven out of 10.