305 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “It’s more efficient for the developers, because you eliminate the need to learn a whole new set of tools if you move from one project or team to another.”

  • “If someone changes a Terraform plan, that goes through the CI/CD pipeline and triggers a GitHub Action that triggers an approval process, just like a pull request for some application code."

  • “Migrating to GitHub aligns beautifully with our cloud-first strategy and moves us further ahead in our journey to modernize processes and support cloud development, mobile development, microservices.”

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

  • “Teams share their work with the larger developer community on GitHub, whether it’s samples, or small projects, or SDKs.”

  • “We want to collaborate with other companies and individuals to bring transparency and compliance to open source licensing. And we’d love to make sure that any information we find goes back upstream. If a project with an MIT license has GPL license code, for example, we’d like to let the maintainers know, so they can update their license information if they choose to.”

  • “By standardizing on GitHub our developers can work the way they want to while still making it easy to share and discover each other’s code.”

  • “Now GitHub does that heavy lifting, and we leverage GitHub APIs to create products that enable our developers to build faster, smarter, and safer. Developers have fewer tools to juggle, which reduces their cognitive load and lets them focus on innovating.”

  • “What GitHub enables us to do is create a ‘parts warehouse’ where developers can find useful code that can be quickly assembled into new solutions.”

  • “It gives us the best chance to stay as secure as possible when writing software.”

  • “It’s more than just source code control."

  • “We clearly needed to find a solution."

  • “GitHub is where the developer community is, and that’s where we want to be.”

  • “Now we’re doing architectural reviews in GitHub as Markdown documents. So if someone has an architectural decision to make, they’ll submit a proposal as a pull request. And that’s the start of that documentation process.”

  • “In the past, the feedback loop was longer. Eventually, it might trickle down from Jira and someone might pick it up.”