GitHub Reviews

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 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. 

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.

We use GitHub as a repository. 

GitHub needs to improve its UI. 

I have been using the solution for four years. 

GitHub is very stable. 

The tool is scalable, and we can leverage our DevOps projects using it. My company has 200 users. 

The tool's setup is straightforward and takes seven days to complete. 

I rate the product a seven 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.

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.

Because Github is hosted in the cloud, we do not require many resources to maintain it. 

The security for this solution could be tightened up and improved. 

We have used this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

We have not needed to contact their support team frequently. 

The initial setup was straightforward. 

The licensing offered is on an annual basis. 

During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently. How useful these features are, depends on each business. 

I would rate this solution an eight out of ten. 

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.