GitHub Reviews

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. 

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.

Syed:
So, basically, I can store my code in some repository, so we can manage also that version control. So, if he developed some applications, so we can manage with versions, so that feature GitHub provide, so we can create some repositories. Through repositories, we can manage the versions, so it's very useful. So, also and that GitHub provide some CI/CD pipeline feature, so we can integrate CI/CD through GitHub, so whenever I commit that code, it will automatically deployed in our servers, so it was a very useful feature in GitHub.

Tutorial videos within the GitHub dashboard will very helpful.

I have been using this solution for one year. 

This is a stable solution. 

This is a scalable solution. We have between 300 to 400 users. There are five DevOps staff in our team who take care of maintenance.

This is an open source solution and does not include licensing. 

I would rate this solution a nine out of ten. 

We use this solution for completing repository services code on Azure. We use it for different customers and to design and test environments. We also use it for some background testing.

We are satisfied with the performance, and we've never had any performance issues because we generally use it on a smaller scale. Using the solution feels like we are running a massive development team comprising a couple of other employees and me. We design the environment and can manage the branching and design better.

There could be more integration into Azure. It will make it easier for us to present it to customers.

We have been using this solution for about three years.

It is stable, and we've never had issues.

It is on cloud, so it is pretty scalable. We use it in the consultancy department to test and see customer environments and errors. It is also good when doing a cause analysis because you can see the code that is being used.

The initial setup was easy.

It is a free solution.

I rate this solution a seven out of ten. I would recommend GitHub, but Visual Studio is arguably a bit better.

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.