GitHub Reviews

Some of the people in my team use this solution for version control of personal projects.

The most valuable feature is help offered by the community for open-source projects.

The ticketing system is not working.

This solution would be improved with the inclusion of support for CICD.

This solution definitely feels stable. I've never had an issue with it.

I've never had an issue with slowness or anything like that, so my assumption is that it's scalable.

We're using this solution for our personal projects, and there are approximately ten of us.

I contacted technical support one time to open a ticket. However, I haven't needed to rely on it. Basically, I'm happy with technical support.

We are currently using GitClub for company projects, and do not have plans to switch at this time.

There is no cost to use this solution.

I have evaluated BitBucket in addition to GitClub and this solution.

This is a good solution, but it really needs support for CICD.

I would rate this solution a seven out of ten.

We use GitHub for the resource management of our central system. We are customers of GitHub and I'm a solution architect.

It's great that GitHub integrates easily with Jenkins. It's helpful for the DevOps as well, checking in and checking out, the solution incorporates well. It's easy to integrate with third parties as well as with other build management tools. It's a really user-friendly tool.

There are some minor areas of improvement that could be made, specifically the onboarding processing which I think could be simplified. It would be great if GitHub could integrate with AI and machine learning systems.

I've been using this solution for two years. 

The solution is stable. 

The scalability is good. We're using it with Microsoft, Docker and Kubernetes, and whenever there's an increase in traffic, we're able to manage that. 

I previously worked on GitLab but find GitHub has many more options and features, particularly in terms of project and SQL management. It was easy to migrate from GitLab to GitHub.

The initial setup is very easy and there are multiple ways to integrate GitHub Dash or to command prompt and that simplifies things. We migrated to pipeline to build and deploy the process. 

I rate this solution eight 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. 

Our primary use case is as a software repository. I've also used it for projects with several developers and a team leader who worked on the source code and put it into the master repository. From there they started the existing CI/CD pipeline which deployed the microservices into the OpenStack. I'm an architect and design the solution, integrating it with the components. We are customers of GitHub.

This is a simple, easy-to-use solution that is fully compatible with Git. 
It's also a good source for training because a lot of source code is open. It's a tool where anybody can share the source code.

I'd like to see a better search function. It can be difficult to find what you're looking for because there are mostly a lot of keywords. If the function were improved it might help in finding some open source code. 

I've been using this solution for several years. 

The solution is stable. 

This solution is scalable. 

I use this solution and recommend it for the source review and also for the CI/CD pipeline.

I rate this solution nine out of 10.