GitHub Reviews

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.

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 used it mainly for version control and when we wanted to test an application at the initial stage or launch the mock-up version.

When it comes to version control, GitHub is fulfilling all that requirements. GitHub is the best tool for source repositories.

You can create public and private repositories.

GitHub could expand the limits of the free version. People are waiting for CNS. 

I have been working with Github for the past eight years.

I consider it stable as of now.

It is also scalable with respect to the branches.

We have not had to use technical support. The documentation that was provided for troubleshooting worked effectively.

The setup was very straightforward and easy for me.

We did not compare GitHub with other options.

I would rate GitHub a nine 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.

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 use the solution when developing new code or modifying existing code, changes are tracked and other team members can review the code before production. 

The ability to track external changes to repositories we are using has been very useful for us. If we have a piece of code that's being implemented and it makes use of modules that we're calling externally from, let's say NPM, and a defect is found in one of those NPM modules, we're immediately alerted that a defect has been found in libraries outside of our code space. This enables us to keep in touch with defects that other people have discovered in the code that we're using. GitHub informs us as other users discover broken code, which allows us to deal with issues very quickly, without investigation on our part. 

The versioning of the code and the tracking of changes are definitely some of my top features. 

The ability to code reviews with peers.

The automatic checking to make sure that any of the code in my repository is not out of date with any modules that I'm making use of.

The solution could have better support for the Markdown language.

I've been using the solution for over ten years, probably since its beginning. 

The solution is very stable, they have been working on it for over a decade. 

The product is extremely scalable. We've seen applications that are hundreds of thousands of lines of code and it doesn't have any problems working with them.

I'm a contractor for the Department of Veteran Affairs, and we've easily got several thousand people making use of the code just within the VA itself. It's being used by almost everyone on a product development team, including project managers, testers, developers, and documentation specialists.

The support is very good. We make use of Slack for communication and we have dedicated technical support for GitHub right in our Slack, which allows us to get responses within minutes from their technical support team.

The initial setup was very simple.  

It really depends on the application we're working on. I've seen deployments take as little as 15 or 20 minutes to push out a code change, up to hours or days depending on the functions that we're changing.

We implemented the solution via an in-house team. 

Due to the cloud environment, we don't need anyone for maintenance, that's all done by GitHub.

We have an enterprise licensing agreement, and I am not part of the finance department so I can't say how much it costs. 

I would rate GitHub a nine out of ten. 

The implementation is a hybrid public and private cloud. GitHub in some ways is similar to NPM, but it is a code repository primarily for code versioning systems. It's all cloud-based and we just upload our code to it. There are functions within GitHub that will take and monitor the code that's uploaded and any NPM repositories that it makes use of, and confirms that your code is making use of the latest code repositories. Anytime there is a discrepancy or an upgrade to one of the code repositories, it lets you know what that upgrade is.

They're constantly making improvements to the environment, adding new features and functionality. The new features and functions that they're coming out with are available to me sometimes before I realize I even need them.

We use GitHub extensively with any new product we are developing and we're going to keep doing it that way. I would advise anyone to implement this solution. 

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.