305 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “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."

  • “As a new Engineer, GitHub facilitated a fast onboarding process and enabled efficient communication between teams within the technology organization."

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

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

  • “We had scaling problems, merge conflicts, and deployments were always an issue.”

  • “Usually a card will be connected to a pull request, so when the next step is a code review, that’s easy for someone to just click through the integration, review the pull request and approve it."

  • "When we created our GitHub environment, we gave everyone on our product team access to it."

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

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

  • “It frees up developers’ minds a lot."

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

  • “It’s an agreement that a piece of code is stable, that it’s passed a certain set of evaluations, and is ready to move from one location to another.”