GitHub Reviews

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. 

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.

I use GitHub for work and personal projects.

With pull requests into the project, all the different repositories are there, and we make the changes there.

GitHub has everything. All the integrations with different applications are really good. GitHub's transparency is also valuable; when something happens, you have a status online.

The solution is really good. I cannot think of improvement needs. 

I have been using GitHub for four or five years.

I faced one or two breakdowns. That said, they lasted only for a few seconds or a minute. However, GitHub keeps us informed with their status updates, so you know it's not you but GitHub, ensuring transparency.

The support team is good. They provide an online status when something happens. It is reassuring to know that it's not your problem but GitHub's, which shows transparency.

Positive

It's really easy to set up. The initial setup and the deployment are also easy to manage.

I do not know about the pricing because I do not pay anything. It's free for me.

I'd rate the solution ten out of ten.

We use GitHub for AI features.

GitHub is a cost-effective solution. The solution provides good customization and support.

I have been using GitHub for a couple of years.

We haven’t faced any stability issues with GitHub.

The solution’s initial setup is straightforward.

GitHub is a cost-effective solution.

GitHub's branch protection feature is effective in our workflow management. I work with the cloud version of GitHub. The documentation is enough to resolve issues with the solution. People working with Microsoft tech can use GitHub. Microsoft is investing heavily in this tool. Using GitHub depends on users' use cases and their technologies.

Overall, I rate the solution an eight out of ten.

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.

I'm mostly using the solution for the backup repository. We are also using it for bug tracking and Scrum management.

I like to do projects using the tool. I also like the check-in and check-out features. The product helps our team collaborate across different locations.

The merging features can be improved. The tool has plugins that allow CI/CD integration. It would be helpful if it were available out of the box.

I have been using the solution for almost ten years.

The product is very stable. I rate the stability a ten out of ten.

The product is scalable. We had 100 users initially. Now, we have reduced it to 50. The solution is used daily in our organization. The usage will increase as our company grows.

I used SVN before. I switched to GitHub due to SVN’s cost.

I will recommend the tool to others. If someone is looking for a repository backup solution, they can use GitHub. It helps with task management. It is helpful in AI development projects. It is a valuable product. It does justice to the price. Overall, I rate the solution an eight out of ten.

GitHub allows us the option to push files from a non-UA method or directly upload files from the UA. You can integrate GitHub with Jenkins to do CI/CD.

GitHub could add some more security features. 

We've been using GitHub for a year. One of our clients advised us to switch to GitHub, so we did. 

GitHub is stable. I haven't had any issues so far. 

We have the option to add storage if needed, so it's scalable. 

We've never contacted GitHub support. If we have a technical issue, I'll usually search for answers online. It's the same with other data tools like Postman. 

GitHub doesn't require any setup. You only need to create an account and a repository. After that, you start adding your files. 

I rate GitHub 10 out of 10. I only use it for storage, so I don't have any problems with it. If you're looking for storing files and code, GitHub is the best and most secure solution. 

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. 

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.

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.