305 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • "GitHub Team allows us to easily scale our engineering team as the company grows. Onboarding is easy—developers automatically have access to everything they need."

  • “It’s a great help in keeping our core platform and intellectual property secure.”

  • "Almost everything we do as a company is kept inside of GitHub Enterprise, from security controls and application code to internal policies."

  • "GitHub is the lingua franca of developers. The more you can make work feel native for a developer, the more positive their experience. Pushing both product development and our beta interaction onto GitHub was a happy experience."

  • "We want them to focus on delivering value to customers, not developing integrations and deployment scripts. We needed a common, modern solution."

  • "They’re eager to make the move, because GitHub is a platform they’re familiar with and it provides them with more possibilities."

  • "It was much harder to collaborate before. Now there are no boundaries."

  • “We have unit tests, we have integration tests, we have browser tests, and tests to see whether the pixels are matching perfectly."

  • “For example, when using VS Code and GitLens we can see who wrote what lines of code. We can also jump straight to the pull requests in GitHub for further context, which is super powerful.”

  • “Any engineer within the company can commit code into our repositories, however, all code goes through a mandatory review process before it’s put into production."

  • “It was the number one most talked about issue in the engineering organization. It had been a while since LinkedIn revamped developer experience, so this was a time for us to revisit that and modernize it.”

  • “But first we had to look at the market and determine what the best fit for the organization would be. We went through a very detailed process of capturing requirements, talking to the customers, and evaluating the workflows.”

  • “That’s why we’ve been conducting usability studies, we want developers to be able to complete their workflows as fast as possible.”

  • “The previous systems were difficult to integrate with. There was limited static analysis that happened in our review pipeline because it was so hard to make issues visible in a way that was both intuitive and helpful to developers.”

  • “We clearly needed to find a solution."