"Before starting this project, each developer did his or her own work. But now, we collaborate with each other very often, and don’t hesitate to ask or share. This motivates me a lot."

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

“For all the CI builds, checking code, and security scanning, developers built their code on their desktop and did a copy and paste to the server."

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

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

“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 …

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

"Our intention is to remove the inequality from the traditional, structured banking system and simplify it for everyone."

“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 …

“When employees join, they have access to most of the repositories across the company, so that any team can benefit from the work other teams have already done, or contribute improvements to code maintained by people in other parts of the company.”

“It’s easier and faster to take action on an alert now, because there are fewer steps they need to take to view and fix an issue.”

"GitHub has the biggest developer community in the world. We knew if we wanted to give our developers tooling that could cross over into other industries and companies our clients would also recognize, it would have to be a product everybody really knew and loved."

“Teams were more likely to use a piece of software from a third party than use code from the team across the hall.”