305 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “That’s why we’ve been conducting usability studies, we want developers to be able to complete their workflows as fast as possible.”

  • “If we deliver a website in an emergency 30 days late, the website won’t be helping our community.”

  • “Our students spend their time building and debugging real applications.”

  • “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.”

  • "Code changes were relegated to a handful of people in an ivory tower. It’s made what we do much more seamless, transparent, and collaborative.”

  • “Whether it’s being initiated, planned, executed, or terminated, the ticket contains all relevant information, including its owner.” They use a template to maintain consistency and stickers to generate a weekly report with the GitHub API. “There’s less manual work, and leads can send stickers out to the wider teams."

  • “Even our infrastructure team is developing code based on GitHub. Since we manage infrastructure as code with Kubernetes and Terraform, it’s good to be hosted somewhere.”

  • “The status quo worked when there wasn’t a need for groups to interact with each other,” he said. “As we expanded the development of more complex features, we saw the need to work differently. That’s when we discovered GitHub.”

  • “Most people that are learning Git are doing it through GitHub and open source.”

  • "GitHub is more than just a place to store code, it’s a full-featured platform where we can manage the entire developer workflow."

  • "It's clear embedding generative AI across developer environments will transform how organizations deliver and drive value and ultimately achieve more.”

  • "Transparency helps us vet the best ideas no matter where they come from. GitHub helps us scale that."

  • "GitHub has become one of our main sources of sharing information across teams and really empowering engineers with more information—from checking out code to implementing new processes."

  • "[GitHub] is a source of truth."

  • “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.”