CirveshDaga - PeerSpot reviewer
Enterprise Architect at Tech Mahindra
Real User
Top 5
Clear licensing model, scalable, and simple implementation
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

GitHub could have better integration or capability with other solutions.

For how long have I used the solution?

I have been using GitHub for approximately four years.

Buyer's Guide
GitHub
May 2024
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
771,212 professionals have used our research since 2012.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

I have not used the support from GitHub.

How was the initial setup?

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

What about the implementation team?

We did the implementation in-house for GitHub.

What's my experience with pricing, setup cost, and licensing?

 The licensing model from GitHub is very clear.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Daniel Piessens - PeerSpot reviewer
CEO at RevealRx LLC
Real User
It's easy to inspect changes and visualize code and differences
Pros and Cons
  • "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."

How has it helped my organization?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using GitHub since 2009.

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
GitHub
May 2024
Learn what your peers think about GitHub. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
771,212 professionals have used our research since 2012.
Vice President at a financial services firm with 10,001+ employees
Real User
Good technical support and highly scalable but the licensing is challenging
Pros and Cons
  • "We've found the technical support to be very helpful."
  • "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."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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

How are customer service and technical support?

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.

How was the initial setup?

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. 

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Rudolf Holzmayr - PeerSpot reviewer
Head of Application Support & Infrastructure at Baader Bank AG
Real User
Provides good version control, but should include some security scanning for new libraries
Pros and Cons
  • "The most valuable feature of the solution is the version control field."
  • "It would be beneficial if GitHub provided some security scanning for new libraries to ensure that there are no viruses in it."

What is our primary use case?

We use GitHub to track what kind of libraries you are using.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using GitHub for two months.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

Which solution did I use previously and why did I switch?

I have previously used Bitbucket.

How was the initial setup?

The solution's implementation takes a long time.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Dilip Telang - PeerSpot reviewer
Director, Talent Acquisition & Staffing at Conduent (formerly Xerox Services)
Real User
Top 5
Easily expandable, great for recruiting, and easy search functionality
Pros and Cons
  • "The solution is scalable."
  • "From the recruiting standpoint, I would like to see email IDs and phone numbers and a brief introduction about their profile."

What is our primary use case?

We primarily use the solution for sourcing candidates.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We did not previously use a different solution.

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

I’m a customer and end-user.

I’d rate the solution eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Information Technology Specialist at Brandix
Real User
Offers time reduction and enables remote work
Pros and Cons
  • "GitHub provides good time reduction and this is what I value the most."
  • "The security point should be addressed in the next release and scaling is also an issue."

What is most valuable?

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.

What needs improvement?

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. 

For how long have I used the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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. 

How was the initial setup?

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.  

What other advice do I have?

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. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Yantao Zhao - PeerSpot reviewer
Software Integration Engineer at Thales
Real User
Top 5Leaderboard
Offers a free version and is helpful to set up simple pipelines
Pros and Cons
  • "GitHub is good for small companies and for personal use."
  • "Though I haven't done much research, GitHub lacks in providing more functions like GitLab."

What is our primary use case?


What is most valuable?

The product can be used to set up simple pipelines. GitHub is owned by Microsoft and is deployed on Azure. If you work offline with Azure, it is very easy to link to GitHub because Azure's cloud engineering is designed to handle a lot of use cases.

What needs improvement?

Though I haven't done much research, GitHub lacks in providing more functions like GitLab. GitHub should aim to provide more functionalities.

For how long have I used the solution?

I have been using GitHub for many years.

What do I think about the stability of the solution?

Stability-wise, I rate the solution a seven out of ten.

The product is becoming more and more complex if I consider how it was in the past. If you search the tool's menu, sometimes the terms are used by clouds like AWS and Azure. AWS has a set of words and terms, while Azure also has a similar set of words. The meaning of the words in Azure is not as straightforward as it is in AWS. GitHub has a lot of new terms, menus, and functions, which are sometimes not very straightforward to understand.

What do I think about the scalability of the solution?

The product's scalability should be fine since Microsoft mostly supports it, and I believe that it is available on the cloud services offered under Azure.

Which solution did I use previously and why did I switch?

I tried to use Atlassian's cloud services, but eventually, I chose GitHub, considering its internal integration with Microsoft.

How was the initial setup?

The product has no deployment phase since the tool has an open-source version available on the cloud.

The solution is deployed on the cloud model.

What's my experience with pricing, setup cost, and licensing?

I use the tool's free version.

What other advice do I have?

The product is used in the development workflow because most of the open source software is in GitHub, so sometimes, just a couple of links to other software can be done easily.

GitHub is good for small companies and for personal use. GitLab is more useful for mid-sized and big companies.

I would not recommend the product for large development projects.

I recently learned more about AI. In the cloud, if I develop an application using AI and link it with GitHub, then I can create a web app linked with the solution. With the use of new codes in GitHub, it can trigger the app to be deployed automatically in the cloud. GitHub is useful for Windows-based applications, and it is the best choice because of the internal integration between both the tools.

In terms of the benefits derived from the use of the product, I would say that if you search for some technical or computer problems or issues, I think that 80 percent of them can be associated with GitHub's sample codes. The product is a place where developers can get clear knowledge about codes.

I use the centralized functions of the tool for my personal use.

Considering that the product is used by small companies or organizations where Windows-based products are used, I rate the tool nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Senior data engineer at 0
Real User
Top 20
Reasonably priced, robust, easy to use, and easy to manage
Pros and Cons
  • "I like the CI/CD features."
  • "The stability can be improved."

What is our primary use case?

We used the product for CI/CD.

What is most valuable?

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.

What needs improvement?

The stability can be improved.

For how long have I used the solution?

I have used the solution for 15 years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How was the initial setup?

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

What about the implementation team?

The product can be deployed in-house.

What's my experience with pricing, setup cost, and licensing?

The product is reasonably priced.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free GitHub Report and get advice and tips from experienced pros sharing their opinions.
Updated: May 2024
Buyer's Guide
Download our free GitHub Report and get advice and tips from experienced pros sharing their opinions.