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.

I use GitHub to keep and maintain my code and have version control. I connect with GitHub through an application called GitHub Desktop.

GitHub's version control is valuable. A recent example was when I connected a website with GitHub, which I developed in my local environment on my computer. I kept updating the plugins directly from my computer, and then I deployed the code through GitHub, which reflected directly into the live website. GitHub sped up the development process, and I felt safe because if something went wrong, I could always go back to my previous code, so I wasn't worried I would break the whole website. It is good for developers because they have version control over their code.

Moreover, with GitHub, finding other people's code is easy. There are a lot of users who host their code on GitHub and open it to the public. Sometimes, you can learn from their code or just use their solution, so it's very good for the developer community.

GitHub is good for controlling and managing the code without destroying it.

It would be good if there were training materials for junior developers.

I've worked with GitHub for about three years.

GitHub is stable.

GitHub is scalable. It's just me using GitHub for my code. But if you had a bigger project with a team, you could always invite anyone to work with the code. GitHub is good for teams because everybody can start with one main code and then open their branch to code freely without destroying any other code. However, there should be one administrator who performs tests to combine each code.

I use the free version of GitHub.

Many big companies use GitHub, such as WooCommerce for example. There are a few ways to use GitHub, like through Terminal. I personally like to use GitHub Desktop because it makes it easier for the user. I rate GitHub a ten out of ten because it is very useful. I remember a time before GitHub when it was quite painful to be a developer. If I'd write code and then want to make an update, I would have to save everything in version one, then version two, and continue doing so for newer and newer versions. Then I'd end up wondering which one was the latest because it was so confusing. GitHub made it much easier to check my code and review it.

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.

We use GitHub for code versioning; with multiple developers working on the same projects. It gives us a central source for our code. We commit our code to the cloud using the API called Gita, which tracks which developers have uploaded the code, which have changed it and so on. 

The code versioning is excellent, and having a detailed log, including every change made to the code by every developer, is invaluable. It makes it so that if there is a bug or problem in the product channel, we can find exactly where it happened and how to fix it.

There can be conflict issues when two developers work on the same file or line of code, and it would be great to see that improved, possibly with an AI solution. 

A great feature would be the AI for code conflicts, enabling us to choose which code edit is the one we want to go with. 

I've been using the solution for about eight years. 

GitHub is stable, and they are improving in terms of security. 

The product is scalable. We have about 20 end users in total. 

The support is average; they can be inconsistent and it would be good if they were more responsive. 

Neutral

The initial setup is a little complex because it requires some knowledge of GitHub and code versioning. Certain steps need to be taken in a specific order, and if any are skipped or done wrong, it can lead to failure. Aside from the mentioned challenges, one staff member can complete the setup.

There is sufficient documentation to help with the setup process.

The setup was implemented in-house. 

GitHub is an open-source product, but when using the free-to-use version, anyone can see the code we're working on.

If you purchase a license, there's an option to make your code private, and our organization has a license.

I would rate this solution a nine out of ten. 

Compared to the competition, I would say GitHub is the best, as it has the most robust security, and most of the developer community is familiar with it. Bitbucket is also an excellent solution with solid security, but more developers would require training.

We use GitHub for source control.

GitHub is convenient and easy to use.

GitHub should provide more integration in their next release, including integrating with Jenkins, CI/CD and Jira.

We have been using GitHub for two years.

GitHub is a stable solution.

The solution is scalable. We have approximately 200 users.

Prior to using GitHub, we used Subversion, or SVN and CVS. We switched to GitHub because of the cloud enablement as well as the ease of use.

I would recommend GitHub to anyone considering implementing the solution into their organization. 

Overall, I would rate GitHub a nine out of 10.

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.

We are actually working with MuleSoft, and for that, we have to build our application. We are working for a company offering hotels and resorts. We are using GitHub for that process. We're building applications on it. 

It's good for branching and keeping the code. Overall, it is a good tool. We can find stable branches there and it is very easy to manage code there.

The interface is good.

We have found that it does allow for helpful integrations. 

It is really simple to set up.

They need to make it possible to recover branches. For any of the branch that does not have PR, that is unrecovered. So there should be an option to recover those branches.

I cannot recall coming across any missing features. 

The user interface on GitLab is better.

I've been using the solution for six or seven months. 

The solution is stable. There are no bugs or glitches. The performance is reliable. It doesn't crash or freeze. 

We have 70 to 80 users on the product currently. We use it on a daily basis.

It's very easy to scale as needed. 

I've never directly contacted technical support. As a developer, I'm not the one who would be contacting technical support. If there were issues, someone else in the company would deal with them. 

I previously worked with GitLab. They are pretty much the same. GitLab does have a very good user interface. That's the main difference.

The initial setup is simple and straightforward. it is not overly complex or difficult. 

As it is a solution that is on the cloud, there is no manual maintenance required. 

We do have a separate team that handles deployment. I don't handle deployments directly myself. 

I don't deal with licensing. I cannot speak to the exact pricing. 

I'm just a customer and an end-user. 

We currently work with the latest updates of the product. 

I'm a developer and I don't work with managing everything on GitHub. I just use it for putting in the code and merging branches.

GitHub actually is a pretty easy tool. It is not very difficult to understand. It is very easy. Everyone can set up branches there or work on it.

I'd rate it eight out of ten. If we could recover branches, I'd give it a perfect ten. 

I use Github to store the code that I write. I don't use it very much. It may be used more by the active developers.

I am using it, it was easy to set up and it is working well for me.

I would want to see some form of code security scanning implemented.

Our company has used GitHub for a long time. I have been using this solution for two and a half years.

We use GitLab release 14.6.7.

I did not have any issues with the stability of Github. It worked seamlessly.

I have not contacted technical support.

Some of these tools are associated with our parent company. We consume them. I believe they were set up by our parent company's tools team.

The initial setup is straightforward.

Client setup takes about 15 to 15 minutes on the workstation where I do my development.

I completed it myself using the documents provided, and I was able to connect it by following the steps.

I would rate GitHub a nine out of ten.