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.

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.

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.

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.