GitHub Reviews

GitHub's workflow is smooth, and it integrates seamlessly with outside projects and libraries. It simplifies our entire development flow.

GitHub's source code management is top-notch. It's easy to inspect changes and visualize code and differences. Their action system is comprehensive in terms of making changes and automation.

GitHub's issue management could be improved a little from an organization standpoint. It would be helpful to have the ability to organize a work board or a backlog more comprehensively. For organizations migrating to GitHub from arbitrary systems, it's a little bit of a headache to move on to that system.

I have been using GitHub since 2009.

We've never had any performance issues with GitHub. I don't think we've had an outage yet and we've been on it for a number of years now. 

GitHub is extremely scalable. We only have about half a dozen repositories in there, but I know some organizations with hundreds working without issue. We're using it extensively. Everybody in the organization is using it, but it's fewer than 50 because our organization's pretty small. We'll increase usage naturally with time, but we're almost close to 100 percent, so it's hard to really increase usage at this point.

I read the documentation, but we haven't had any need for tech support.

We were using Azure DevOps previously, and we switched to GitHub primarily due to cost. The automated build platform is costly on the Azure DevOps side but significantly less expensive on the Azure side.

Setting up GitHub is extremely simple. You create an account in five minutes and have your first repository set up in another two after that. You're up and going in under 10 minutes.

It's a lightweight solution. The only maintenance is usually related to active stuff that we're doing on the platform. I wouldn't classify that as maintenance. That's product improvement.

We are a step above the base package. It's not the enterprise package. We're using the teams or the organization package. It has a few different names.

I rate GitHub nine out of 10 for overall ease of use and completeness in functionality.

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 use GitHub to track what kind of libraries you are using.

The most valuable feature of the solution is the version control field. GitHub has a good integration and coding engine.

It would be beneficial if GitHub provided some security scanning for new libraries to ensure that there are no viruses in it. The solution’s stability could be a bit better.

I have been using GitHub for two months.

I rate the solution a seven out of ten for stability.

Around 30 users use the solution regularly in our organization, and we plan to increase the usage.

I have previously used Bitbucket.

The solution's implementation takes a long time.

We pay a licensing fee for GitHub, which could be cheaper.

The solution is deployed on the cloud in our organization. I would recommend the solution to other users. GitHub is a version control, and you can always switch and text because every version is saved.

Overall, I rate the solution 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 used the product for CI/CD.

I like the CI/CD features. The tool was easy for me to use because I had used it for a long time. GitHub is a leader in the domain. Others copy GitHub.

The stability can be improved.

I have used the solution for 15 years.

I rate the tool’s stability a ten out of ten. The vendor modifies many things and provides new releases regularly.

The tool is very scalable and reliable. There is no loss in quality.

It is easy to set up the account and give permissions to others.

The product can be deployed in-house.

The product is reasonably priced.

I have also used GitLab. There is not much difference between GitLab and GitHub.

I used GitHub in my previous organization. In my current organization, we mostly use Azure. GitHub is easy to use and easy to manage. It's good for integration and for multi-worker projects. It is robust. Overall, I rate the solution a nine out of ten.

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.