305 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “As more micro-services were added, and the team size grew, the number of SVN repositories increased. It became difficult to manage the complex codebase with a large team. Our code review cycles were taking a lot of time that slowed the team down.”

  • "We are already seeing our early community open source their own code to encourage growth in the group and have fun with people building on top of their code, Lynda said. For example, one Jibo developer produced an If This, Then That (IFTTT) capability for Jibo and shared the project. …

  • “You can’t do that with a file system or database. And you don’t get a history of changes. When you treat GitHub as a universal tool, it creates a lot of opportunities and introduces interesting new workflows to the process.”

  • “Some brands are working with bleeding-edge technologies, others are battling legacy systems.”

  • “We get everything we need from the GitHub Actions marketplace to build and support our tailored CI/CD pipeline.”

  • “GitHub Advanced Security has put us in a position to confidently talk about our security posture when it comes to source code."

  • "By providing a platform that integrates with lots of different tools and supports many different workflows, we’ve provided the greatest common denominator to our developers, while capturing the greatest value for JPL—a single location where developers can find code that solves JPL’s problems."

  • “We want to make sure that the task we’re doing manually today becomes mostly automated. We focus on building tools that serve as an enabler for developers.”

  • “Open source fits in by providing a new level of transparency, revealing the code behind the science. In the last few years, we’ve open sourced several projects, contributed code to the Apache Software Foundation and the W3C, and funded existing open source projects.”

  • “We opted for GitHub Enterprise for the major functionality: pull requests, easy merging, team collaboration, and overall simplicity.”

  • "We opted for GitHub Enterprise for the major functionality: pull requests, easy merging, team collaboration, and overall simplicity."

  • "As we got to know GitHub better, we began to develop process around the tool, and became more rigorous about release drafts, pull request labels, and milestones. As our engineering organization grew, we relied more heavily on teams and roles to control the flow of features."

  • "Knowing GitHub is rolling out features that we can incorporate into our existing workflows, is reassuring. Having all our key features centralized on one platform is a game-changer."

  • “We believe that satisfaction is a strong contributing factor to developer enablement, and since Copilot improves how developers work and engineer satisfaction, we’re giving our entire team access to Copilot."

  • “GitHub, in terms of cost and performance, is head and shoulders above everything else.”