GitHub Reviews

I use GitHub as a code repository, and we use GitHub Actions a lot to trigger our pipelines.

The most valuable features are GitHub Actions for triggering workflows, GitHub Secrets for saving credentials without needing a third-party service, and the UI for identifying errors in the code when we commit.

Regarding improvements, I preferred the tool's earlier pricing model, which limited storage and the number of repositories instead of the number of users, which was more convenient from a customer perspective. I've also experienced issues with GitHub servers being unable to support moving repositories, which caused problems. For basic plans, no support was available to help resolve these issues. I think GitHub should provide more support for smaller businesses to help with these problems.

I have been using the product for six to seven years. 

For stability, I'd give the solution a seven because we faced 500 server timeouts a couple of times under a heavy workload. It's a good product; otherwise, that was just one instance I could think of.

I recommend GitHub for small, medium, and large companies. However, for very large businesses spending a lot of money, there are other options with more functions and features.

I rate the product's scalability a nine out of ten. 

The community support for GitHub is good enough. However, the official support from GitHub itself is not the best.

The initial setup is quite straightforward. The UI is interactive, so I don't see any problems there. It should be fine with any issues. I'm using the cloud-based version of GitHub.

Regarding pricing, I'd rate it eight out of ten. It's decent and not too expensive, and small businesses can also afford it. With AWS taking CodeCommit out of the market, I don't see many competitors for small companies in terms of GitHub.

There are options like GitLab with more functions and features for very large-scale businesses that spend a lot of money.

I'd give GitHub a nine out of ten as a product and would definitely recommend it to other users.

Our primary use is for open-source code management and distributed version control. We use the solution to coordinate the work of developers, assisting them in developing and maintaining our source code. We also use the tool for code review purposes using the GitHub repository, where I can comment on or review lines of code for developers to edit and improve performance. They then receive a notification alerting them of the desired update, which the project developer and project lead can approve.

The best feature is the ability to track the history of all code changes, and it's easy to use. Additionally, as it's open source, anyone can use that feature resulting in distributed development. This opens the door to collaboration with different code and developer, feature, and master branches of development.

The solution also features robust security, high speed, and good integrity.

Excellent code management means that, even when developers accidentally delete sections of code, it's easily retrievable. GitHub reduces developer workload and saves them time.

The GUI design is poor, so I exclusively use the CLI, which is much easier to use and understand. It would be great to see the GUI updated to be more user-friendly. 

It isn't possible to run different branches simultaneously, and it would be good to see support for that.

We have been using GitHub for over seven years. 

GitHub is very stable; we can use it throughout the development process.

The solution is highly scalable. We have between 100 and 150 end-users, both developers and testers.

We haven't encountered an issue we couldn't fix ourselves or by using Stack Overflow or Google, so good community support is available.

The initial setup is very straightforward; creating a repository and the paths required for local and other branches is easy.

The deployment time depends on the project size. We follow an agile sprint cycle so we can carry out new deployments every one to two weeks, and they don't take much time at all.

GitHub is an open-source application. It's free to use.

I would rate the solution an eight out of ten. 

We use GitHub because it's open source and makes code management straightforward; it's simple to track different code versions and change history. It's an easy-to-use, efficient application.

For someone looking to use the solution for the first time, I would say it's straightforward and possible to learn the significant features in a day. Learning to clone projects, push and pull code, and use comments is simple.

We are using GitHub as a repository for a couple of customers to be able to do Infra as Code in Microsoft Azure for them.

The most valuable features of GitHub are the ease of integration into Microsoft Azure DevOps. The process that you need to deploy into Microsoft Azure becomes fairly simple and the templates are already available, a lot of the engineers find it easier to use.

GitHub could have better integration or capability with other solutions.

I have been using GitHub for approximately four years.

GitHub is highly stable. Our team has not had any trouble with it.

The scalability of GitHub is good. I have not come across any limit.

We have six people using this solution in my organization. We have plans to increase usage.

I have not used the support from GitHub.

The initial setup of GitHub is simple. The full implementation took approximately a few hours. There was some user configuration that took some time.

We did the implementation in-house for GitHub.

 The licensing model from GitHub is very clear.

I recommend this solution to others. There may be some customers that are very picky about not having code on the cloud, and then my recommendation would normally be to use Microsoft Azure Repos, which is essentially a clone of GitHub but it stays within your subscription and within your tenancy on Microsoft Azure.

I rate GitHub a nine out of ten.

Currently, the solution is our source control system. We manage the DevOps pipeline for the company and it's the version control backbone.

I'm curious as to what DevOps Tools can be integrated into GitHub to get it to be on part with the capabilities that come out of the box in GitLab, or whether we should just switch to GitLab to get all of those capabilities.

The stability is quite good.

The scalability is excellent.

We've found the technical support to be very helpful.

Overall, it's a very good product.

If it had all of the end-to-end integration, then we probably wouldn't have any doubts about what we have installed. However, at this point, we're still trying to figure out how to use it end-to-end. 

The new version is supposed to make GitHub actions available to us within the on-prem instance. We're waiting for that, just to see how that plays out with the rest of the source control features and to see if that gives us some semblance of similar capability to what GitLab supposedly provides.

I don't know if there are any plans to do a better integration with the front-end type of tooling. I would like to see it evolve to a full-blown DevOps stacks hopefully similar to GitLab at some point.

We've found the way licensing is set up to be very challenging.  Also, the LDAP sync capability falls over frequently due to the complexity of our LDAP domains.  This requires us to perform manual LDAP syncs almost on a daily basis

I'm new to the company. That said, I would guess that the company has probably been using the product for about three to four years at this point. It's been a while. I've used it within the last year and I'm continuing to use it regularly.

As far as stability goes, it's been good. We haven't really had a lot of major issues yet. There are no bugs or glitches. It doesn't crash or freeze.

It's obviously very scalable. We have thousands of users on it and there are no concerns.

We have a monthly call with the technical sales folks. They look after our every need and they're very technically knowledgeable as well. If we go through support, usually issues are resolved fairly quickly. There are no complaints there. We're very satisfied with the level of support on offer.

I just manage the team. I've not involved in the more technical details. I wasn't present for the implementation process. I can't speak to how easy it was, or how difficult, via any first-hand knowledge. 

The licensing model that they have is annoying. One of the things that we struggle all the time with is people that have left the team or the group. We have lots of application teams that are using GitHub. People are moving constantly between organizations, they're moving to different teams, they're moving out of development. 

There's really not an easy way to track who's still using licenses. If they've vacated the position unless somebody goes back into the active directory and actually removes them from the group, they're still holding onto a seat and we're still trying to figure out, how to manage this so that their seat automatically gets reclaimed when people are moving around and it's not a very straightforward process. It takes a lot of effort on our part to try and keep the inventory seats available and managed properly.

We aren't partners. We are simply customers and end-users.

We are still on the previous version. We are still waiting for more stability from the latest version before we update everything.

It's a great product. That said, it needs some work still to be able to do everything that GitLab can do, for example. I'm not sure what the future plans are for GitHub. I know they're working on adding a lot of capabilities now that they're part of Microsoft. They're probably going to make it a much more robust solution - not just a version control system. My perspective is as an enterprise on-prem user. I don't know from an open-source community standpoint, how they feel about the changes. I'm sure most of the users are pretty happy with it as a hosting platform. However, my need is specific to my organizational uses.

I'd rate the solution at a seven out of ten.

We primarily use the solution for sourcing candidates.

I like finding individuals with more repositories and more followers, et cetera. It’s great to find the talent who is available and has particular skills.

The solution is scalable.

I do not think they have to increase storage. There’s enough.

From the recruiting standpoint, I would like to see email IDs and phone numbers and a brief introduction about their profile.

I’ve been using the solution for about a year.

The solution is very scalable. It’s expandable if you need it to be.

I’m not sure how many people use the solution in our company.

I’ve never used technical support in the past. I can’t speak to how helpful or responsive they would be.

Positive

We did not previously use a different solution.

There isn’t really an initial setup to deal with.

I can’t speak to the exact cost of the solution.

I’m a customer and end-user.

I’d rate the solution eight out of ten.

GitHub provides good time reduction and this is what I value the most. My team uses GitHub for working remotely. Security is also a good feature of the solution. It's as if the solution creates a security barrier in the server, whereby I can push changes they make to my server once they come to GitHub. 

The solution has a lot of features. Should my developer leave tomorrow, the changes he has made will remain, even as another developer could do the work.

The branches created for the separate software and enrollment should be improved. There is a need to create separate software branches, such as for the production, operation and development teams, who are licensed, in respect of their need to match to test what they develop in a test environment. I can immediately go back and look at the features to see if they are up to the mark, such as those involving unnecessary code. 

As someone who works in infrastructure, I know how hard it can be to create things on this level, but it can be worthwhile. Confirmations and requisite future updates are in the end user's domain. The migration of the databases, such as the migration of my websites to the new WordPress sites, works at times but is slow. In such a case, the hardware must be increased. When it comes to the question of whether we should change to new servers and set up a new infrastructure level, I have found GitHub to be very helpful. It pushes the code directly to the repository and dumps the database on the other end. 

The security point should be addressed in the next release. Scaling is also an issue. If the code is very high on the user side and I should suddenly find myself wanting to increase the monthly use of my website from 10,000 to 30,000 people, it can create an imbalance in the infrastructure. In the case of the code level, we may see issues involving optimization. 

I have been using GitHub for more than seven or eight months. 

The solution is easily scalable and encourages migration. While I have other products at hand, GitHub makes things fun. We wish to lead and expand. We want to scale this project to the next level, since we have certain customers in hand.

I had to make use of technical support two months back, when I first started working and had a learning curve. This was while I was exploring new ideas as relate to my infrastructure experience. When encountering changes to the core side or the scaling, it is necessary to make use of technical support. An abrupt increase can cause problems with the infrastructure, so I am looking for solutions that will not require me to make changes to it each time this should occur. GitHub allows the core to be scaled up with ease and it offers auto scaling. 

There is a certain amount of difficulty involved in the work we did with the developer. This is because we use private repositories, not public ones, for security reasons and this requires the developer to have a code for a secure shell. 

When we do the initial setup in the cPanel, we are supposed to utilize it for our infrastructure. The enrollment is set up to the cloud and the cPanel and GitHub to the local systems, wherever the developer may be found. Usually, they are remote. We have confidence that the developer reposits first to his local system and from there to the cloud and we must execute shell for these development purposes.  

Our initial deployment was with Cloud One. The cPanel is the browser involved. We make use of WordPress.  

GitHub is the perfect tool for use at present and is extremely necessary. It is one of the best solutions out there. Apart from GitHub, you need to use the local Git version control system since it involves code on a cloud platform. Git version is very helpful. One could download the large types of codes to do on the core level so that there will not be a need to go to the cloud setup every time. The code commands can be run from the local system. Setup and migration can be done with ease. The person would set up the order and the view. In my experience, GitHub is very easy to operate. 

I rate GitHub as a perfect ten out of ten. 

I previously used different tools. At present, I am utilizing GitHub and providing assistance with cell phone numbers. The solution allows me to make workspaces and perform changes with ease. It also allows for easy monitoring. I receive updates from Slack for confirmation purposes. There is no need to wait on my developers, as a connection can be made with the production server. 

We just use GitHub for the repository in our company.

So we have a central repository. So, we do recommend the need to push and pull everything, and that's how we use it.

The requests, push, pull, merge, and everything else in the solution are its valuable features. Later, people make their changes.

I don't have any comments on the improvement needed in the tool since I'm okay with it. I don't have anything really in mind. It's not like I am picky, and I don't need to be picky unless it's really an overblown, like, there are some bugs or some glitches or something like that in the solution. As of now, everything looks fine.

Scalability is an area with a shortcoming, because of which it has room for improvement.

I have been using GitHub for more than five years. We just use the solution for work in our company.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

We plan to increase the usage of the solution. There are a lot of products out there in the market, but I wouldn't say I would recommend it, but if you use it, then it's fine. I don't really compare much as long as that's what is expected from the solution functionality-wise is fulfilled. So, then I am fine with it.

I don't use the solution's customer support.

Regarding the initial setup, I rate it an eight on a scale of one to ten, where one is difficult and ten is easy.

The solution is deployed on a private cloud since it is a corporate thing. We don't go for a public cloud.

The deployment is fast since we just have to run the script, and once it's done, it takes a few minutes.

My company has schedules, and we assign people to do the deployment. So, it's rotational. Let's say I do the deployment this week, and then another person does it next week.

I don't know about the solution's cost. My company purchased it. Before, we used to receive the free version, but then they purchased some of the features.

I am using the solution, and I am fine with it. I would definitely recommend the solution to those planning to use it. I rate the overall solution an eight out of ten.

I am a senior product development engineer and I use GitHub in this capacity.

Essentially, this is the Git product, but in the cloud.

The most valuable feature is the fact that it's cloud-based, and we don't have to manage an on-premises server to use it.

It would be better if the amount of storage were increased.

We have been using GitHub for between six and twelve months.

GitHub is a stable solution.

This is a scalable, cloud-based product. We have a small team and do not plan to increase the number of users.

We have never needed to contact technical support. Any problems that we have had, we have always been able to solve.

I would rate the technical support a two or three out of five.

Neutral

I have used on-premises repositories but it was a long time ago.

No installation is required.

There are no licensing fees for the features that we use. We are on the free tier.

This is a product that I recommend for developers because everybody in the software development field is using it.

I would rate this solution an eight out of ten.