305 GitHub Testimonials

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

“We’re a developer-first organization and we live and breathe GitHub."

“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."

"Now that nearly all of our repositories have been migrated over to git and managing access and collaboration through GitHub Enterprise, we’ve really been able to leverage a consistent version control setup and tools such as Jenkins-CI to manage environment updates and deployments."

“From our DevOps COE, we are now supporting over 25 engineering teams all over the world. By using standards and automation, we avoided those teams performing over 100 manual steps over three months—their DevOps journey is now three steps and less than a day—that led to huge efficiency return to the development teams, and a one-off cost saving for McKesson of $350,000 per team.”

"They like to see things right in front of them, and GitHub gives them visibility into how others are using tools in the stack. When they see how other teams are implementing these tools to do great work, they’ll be more inclined to collaborate and adopt these solutions as well.”

“That’s what I love about GitHub. We can scale and build projects on a new level now. It’s not about how good you are alone. It’s about the greatness we can achieve through sharing and collaboration.”

“The whole focus is on how my everyday job can be put to good use for the whole group. That’s what I love about GitHub. We can scale and build projects on a new level now. It’s not about how good you are alone. It’s about the greatness we can achieve through sharing and collaboration.”

“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."

"With the help of Git, we’re seeing faster code pushes and pulls. We also take advantage of GitHub’s collaboration tools, for both code and the processes (such as issue tracking) and documentation needed around the code."

“During the process, we’re available for any issues or questions. We want to ensure the team is only publishing source code that everyone is behind—open source is about discovering what you need but also giving something back.”

"We chose GitHub not only because it was more affordable but because we’re able to contribute to the greater open source community."

"Before we were using GitHub, we could count on chaos during rapid development phases. With SVN, it always felt like someone was in your way. Or, developers would just work around the version control system and compromise code quality."

“We want to make sure Plaid engineers are happy and that their tools aren’t getting in their way.”