GitHub Reviews

We use GitHub to manage repositories, pull requests from partners and merge new changes. 

The principal benefit of using this solution is being able to organize improvements and changes to code. This is particularly useful for projects which involve many people.

The control version functionality for this solution has been most valuable, especially when managing projects with multiple versions. 

The descriptions within Github could be more user-friendly to show the trees of Gitflow.

I have used this solution for ten years. 

This is a scalable solution. 

We have not needed to contact customer service. All the information we have needed has been available on the web. 

The initial setup is straightforward.

I would rate this solution a ten out of ten. 

GitHub is used to manage distributed versions of systems to allow developers using production operating systems to work without distributed dependency. It is a distributed version control system where we get the repository downloaded on our laptops and can work without any idle time.

Any complex banking can be handled very easily in GitHub. It allows us to integrate with tools like Grid, where we can merge and resolve conflicts without any hassle. 

This solution could be improved if migration was fully automated to make it easy, for example, to migrate repositories into GitHub. 

I have used this solution for eight years. 

The customer service for this solution is not great. The team either takes a long time to respond or doesn't respond at all. 

Neutral

I have previously used ClearCase and Submersion but have used GitHub for the past eight years. ClearCase is a centralized system but has expensive licenses and running processes within the system took a long time. This is the reason we moved to Github.

The initial setup is straightforward and only involved four to five steps. 

I would rate this solution a ten out of ten. 

We are an IT service company that specializes in DevOps, and we use many tools for application lifecycle management, such as GitHub, GitLab, SonarCloud, SonarQube, Docker, Kubernetes, and Azure DevOps. 

We mainly use this solution for storing the code of our applications and our scripts. We also use it for our automated functional testing and for building applications and releasing applications. It is also used to manage our team and our product, as well as to check the security of our product. 

We are a partner and reseller, and we use GitHub Cloud.

All the features are valuable, but the most important feature is that GitHub has advanced security. The second important feature is the capability to create custom GitHub actions and the capability to deploy in different types of architectural infrastructures, such as hybrid, private, or public.

It is not technical. It is more about how people perceive GitHub in terms of the security of the code. They need to understand that if they have a repo on GitHub, it is not public for everyone.

They're improving the work items to track the progress of the team, but in my experience, Azure DevOps is better in this functionality. GitHub needs to improve the form to track the progress of the work done by a team.

I have been using it for more or less one year.

It is, for sure, stable.

It is definitely scalable.

They were very helpful.

I have experience in many tools. GitHub is not the hardest, and it is also not the easiest. It is of medium level.

I would advise trying out the Advanced Security model, which is its best functionality.

I would rate it a 10 out of 10.

Our primary use case of this solution is for collaboration, code sharing, and as a testing environment. We can put it into Docker and create images. I'm the technical lead in the company and we are customers of GitHub. 

GitHub has enabled the CICD pipeline. Without GitHub, we wouldn't be able to do that. 

The code sharing and updated history are valuable features, the capability to roll back to a previous version is very useful. We're also able to make a branch and a merge and it's easy to collaborate with our teams. We can hook up with Jira, with Wiki, and OpenAPI. We have access to all the features we require right now.

I'd like to GitHub become a more user friendly solution. There are some commands that if we want to reset it to a previous version or we try to roll back, we sometimes get a broken link in the history. Maybe there's something we can do to make the learning curve easier for the user. Perhaps by visualizing the operation instead of the command line.

I've been using this solution for seven years. 

The solution is quite stable, we haven't had any crashes.

We don't require much scalability. There's the tech team and then we have around 100 developers, managers, some architectural cloud engineers, and a test engineer. They all use GitHub. We don't require maintenance but we have a cloud engineer who is mainly on AWS services. The only thing that I think they need to deal with is generating tokens for new users. We use the solution extensively.

I have previously used SVN but I prefer GitHub, it seems to be more powerful than SVN. We have a centralized website and a better user interface. 

There's no real setup required, we just installed it and hooked it up to our project, and we put it into the Docker file. Not much setup.

We pay an annual license fee.

This is definitely the best solution I have tried so far. That said, I believe it has some space to improve. It's important to do some homework before implementation and I would suggest using the documentation posted on GitHub. 

I rate this solution an eight out of 10. 

GitHub is specifically designed for repositories and it works perfectly for storing code. We use it for our source code repository.

While using the solution when merging two code branches the code becomes a bit messy. This should be improved in the future.

I have been using this solution for approximately six years.

The solution has been completely stable.

The scalability is good. We had 20 developers using the solution and now we have 200, there have not been any problems.

The technical support was very good.

Out of all the solutions in this category, I would recommend this solution to other companies.
I rate GitHub a nine out of ten.

The initial setup was straightforward.

The price of this solution is reasonable.

Out of all the solutions in this category, I would recommend this solution to other companies.

I rate GitHub a nine out of ten.

We are mainly using it for product development. Our repo and code are in GitHub.

It is a cloud-based solution. It is a part of our subscription in the cloud, and we have its latest version.

It has a lot of features from the code development perspective. You get a lot of features such as repo, commit, merge, and branch. You can play around and do things on the fly.

It is easy and simple to deploy. It is also easier to use when working from home.

It is currently only from the development perspective. It doesn't have features related to project management and testing. It is not like Azure DevOps. So, there is a lot of room for improvement.

It is a version control product, and it would be good if they can come up with a complete DevOps product.

Its stability is good.

Because it is cloud-based, you don't have scalability-related issues. We have around 30 users.

We didn't have to contact them because it is very user-friendly and easy to use. For any help, you can go to the communities.

Its initial setup is straightforward and easy. It is much easier and simpler than Azure DevOps. This is something that Microsoft has to aim for.

It is open-source. There is no license for GitHub.

If you are a startup or have a small team, it is a good platform to start with because you can achieve your business goal without any cost. It provides a lot of flexibility, and you can structure yourself for any kind of product development.

I would rate GitHub a nine out of ten.

We use the solution to handle our switch control. All our first code force is managed by GitHub to commit new features and create different branches. We even use this to manage the code to handle flows and processes. We can use it to create some branches and manage the code ownership, and we have an account for each developer so that they can submit pieces to code review for the user. 

The way we can manage the system is very useful. It'd great for managing code. 

You can have the main branch, and then create another branch, and easily merge them together if you like. 

You can effectively manage code reviews by issuing pull requests. Fellow developers can review my code, which helps ensure that the code is written correctly and clean. It's a useful exchange of information. 

The flow process helps us keep our applications stable. The released version is always running smoothly.

Once you get familiar with the system, it's very easy to use.

The product has a very user-friendly interface and user-friendly security.

There is a bit of a learning curve. At first, you'll have to do some searching online to figure out how to perform or reverse certain actions. When we have new team members, they tend to send you a full request for issues and it can create a bit of a bottleneck. There can be a lot of research and lots of problems initially created by users that don't yet understand the system.

The solution could use even more integration with automation tools. 

I've been using the solution for a while.

The stability is quite good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

There are four teams working with GitHub currently in our company.

I haven't had the chance to contact support, and therefore cannot really comment on how helpful or responsive they are. 

Within the company, we have specialized people who are maintaining the server. From my own experience as a software developer, outside the company, using the public community GitHub has on offer and publishing questions to it allows s to find the answers we need. The community is really responsive to us.

Initially, when I first joined the company, they were using another solution, and recently we decided to move to GitHub. We are currently using it on a daily basis.

There are other solutions that we use for source control and they're going to be migrating to GitHub.

I did not really work on the deployment per see. However, it is really easy to create new branches. There are also great opportunities for integration with other tools, for example. There's some great automation, for example, which is helpful.

I personally use the free version. the company has the enterprise version of the solution. I'm not a part of the licensing process internally and therefore do not have details in regards to how much the company pays to use the enterprise version,

We are just customers and end-users.

We are using the latest version of the solution. We have some internal solutions deployed. We have our own private server, a GitHub server, and it always is properly maintained and always updated with the latest version for better performance.

I would recommend the solution, however, I would suggest those who intend to use it get the proper training on it first.

I would rate the solution at a nine out of ten.

My primary use case for GitHub is for my private projects that I'm developing for my customers. Some customers have their own developers and I sometimes support them to achieve their goals. So we share everything. We're also using GitHub for the documentation for the teams. I also give lectures for the organizations because sometimes they have development teams but they are not qualified enough, so I have to give them some training on it.

The features that I have found most valuable are that it can support you for most of the road map and it can automate some tasks which works really well with collaboration with the teams. They are really interested in how they organize the history of the code itself which is good.

In terms of what could be improved, I would say the security. I didn't try the two-factor authentication so I don't know if they have it already or not.

I sometimes found it very difficult to connect it with other tools, such as Jenkins or others. For the testing for example, I have to go between both sides. I don't know if I am using it right, but I don't know if they have these features or not. So I have to find other tools to support it because I couldn't really rely on GitHub for the steps that I needed.

Additionally, we are facing really big issues with the Arabic language in GitHub and I don't know if they are focusing on some improvement in the language capabilities. This is one of the things we're facing. 

As I mentioned, for the management we need some improvement in GitHub. It's not built for that. We really need some improvement for the project. It made it tough.

But overall I didn't find anything really urgent needed to improve.

I have been using GitHub for about eight years now.

I'm always using the latest update. In my service behavior I always update all the solutions.

GitHub is very stable.

Since I am working as a contractor in our organization and I'm doing the development work as a site project manager, I don't have a fixed team. But we can say that for each project it's about 10 to 20 people using GitHub most of the time.

It is used on a daily basis.

It is easy to add new users.

I was previously using Jira and Bitbucket but now I'm 100% in GitHub. I switched because of my team - they didn't work on Bitbucket. This is the reason I left Bitbucket even though GitHub is more costly.

I was looking for a management tool. Of course, Jira is the first try. When I looked at it for the cloud there were two options - GitHub and Bitbucket. But when comparing Jira's license to the licenses for Bitbucket or comparing the price between Bitbucket and GitHub, I found it's really cheaper for me to have Bitbucket. But because my team was most familiar with GitHub I decided I had to go with it.

The project management sector really needs some improvement for GitHub. I don't know if GitHub made sense for me as a project manager. But for what it was, it's a really good tool.

The initial setup was okay. It is not really difficult from my perspective.

It is so easy. It took about five minutes maximum. It was really easy to configure. But, as I told you, I couldn't figure out how I can use it with my local IDE or development IDE like VSCode or something like that. That's why I'm using Jira. If I use Jira I couldn't change the issue from GitHub to task. In GitHub I found it to be difficult with this.

I did the installation myself.

My recommendation for anyone thinking about GitHub is that it is the best solution - except for the price.

On a scale of one to ten, I would give GitHub a nine.