GitHub Reviews

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.

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.

The solution is used by developers to work as a team on a code. 

The control is the most valuable feature as developers can work on a single code. 

The initial setup requires heavy documentation which can be challenging for new developers. 

I have been using GitHub for more than a year. 

The solution is stable and I would rate the stability a ten out of ten. 

It is a scalable solution. 

Previously, we used IBM but because of the clients' requirements, we decided to move to GitHub. 

The initial setup is mostly straightforward. The deployment takes one hour. 

I would rate the overall solution a ten out of ten.

The solution is used to store code. It is a repository manager for our code. We can also configure it to run our deployment.

It is a good product. The tool doesn’t incur a lot of cost. It is highly stable. We can easily integrate our deployment to achieve continuous integration and continuous delivery.

The product must document the CI/CD process more. It must also expose the APIs for CI/CD.

I have been using the solution since 2016.

I rate the tool’s stability a ten out of ten. It is highly available. I have not encountered any issues.

I rate the tool’s scalability a ten out of ten. I have not encountered any issues with the scalability. I am using the tool for my personal projects. If I needed someone to collaborate, a maximum of five people would have access to the tool. I do not have plans to increase the usage for now.

The solution is cloud-based. I do not have to deploy it.

Our code is secure. We can easily roll back the changes. We can take features to the market a bit faster.

It’s an open-source solution. We do not have to pay for it.

I will recommend the product to others. Overall, I rate the tool a ten out of ten.

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.

GitHub is an excellent platform for organizing all sorts of information. I personally found it beneficial for keeping track of my coding projects, and recommendations, and occasionally making commits. By creating branches, I could easily focus on specific areas and even delve into things like creating my website using GitHub pages. Overall, I found these features to be very practical and advantageous.

In my case, I prefer to keep my repositories public, especially for small-scale organizations that don't require a high level of privacy. I find it useful to maintain a public profile because it allows me to showcase my work whenever I'm looking for a new job or updating my profile. By doing so, others can visit my profile, review my details, and verify the accuracy of my work history. This way, I can confidently stand by everything that I have accomplished throughout my career.

The most valuable feature of GitHub is version control and continuous integration.

The solution can improve by adding video guides, official guides, or short courses that cater to beginners who are new to the system. These resources could offer step-by-step guidance on how to use GitHub, including common procedures such as pulling and committing. Currently, many of us have to resort to searching for information on how to do these tasks via Google. An official guide provided by GitHub itself would be a valuable asset to newcomers and would save them time and effort.

There is potential for GitHub to enhance its features to be more like a Jenkins pipeline or CI/CD pipeline. While I currently use GitHub for code integration, I would like to see more emphasis placed on code management and automation. It would be beneficial to have more input on these areas within GitHub.

I have been using GitHub for approximately five years.

The stability could improve.

I rate the stability of GitHub a seven out of ten.

We have approximately 20 software developers using this solution.

I rate the scalability of GitHub a seven out of ten.

The support could improve. I have received online discussion forum support but it could improve.

Neutral

We might be switching to GitLab.

I rate the initial setup of GitHub a seven out of ten.

I am using the free version of the solution. However, there are some costs my organization pays.

My advice would be to take some time to clean up your repository and organize your data, step by step, in order to optimize its performance and make it more user-friendly. It can be challenging to work with applications like this when there is a lack of resources or input. However, by investing time in making your repository more efficient, you can reduce the potential for overwhelm and streamline your workflow.

I rate GitHub a seven out of ten.

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.

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.

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.

GitHub is essentially a repository of code. It's where you source your code with the client and allows you to use Git. You get versioning and everything else for multiple deployments or codes. That's how we use it.

We stopped the development code on our machines, and we moved everything to GitHub. So, everyone is working on the latest code no matter what we do.

The accessibility is free.

There is room for improvement in terms of interface because  I had a problem with developers who didn't know what GitHub was, and it was a little bit strange to explain. 

I have been using GitHub for three years. We use the latest version. 

I would rate the stability a ten out of ten.

The scalability is very good. It has never let me down.

The initial setup is okay. You need to know what you're doing.

I saw 100% ROI. 

Price is free. 

It is way better than developing software by yourself. I would definitely recommend using the solution.

Overall, I would rate the solution a ten out of ten.