“We invented these amazing applications. So what goes on with our PDF group is very different than what goes on with Photoshop or Magento.”
"We want them to focus on delivering value to customers, not developing integrations and deployment scripts. We needed a common, modern solution."
“Before GitHub, you would have one system for your version control and another for project management. Trying to integrate between them could be difficult."
“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.”
"They’re eager to make the move, because GitHub is a platform they’re familiar with and it provides them with more possibilities."
"It was much harder to collaborate before. Now there are no boundaries."
“We clearly needed to find a solution."
"We are already seeing our early community open source their own code to encourage growth in the group and have fun with people building on top of their code, Lynda said. For example, one Jibo developer produced an If This, Then That (IFTTT) capability for Jibo and shared the project. Another developer built upon that, creating a home automation capability for Jibo, which allows our little guy to turn on lights, televisions, and more. Of course, GitHub is at the center of this effort."
"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."
“GitHub just works. when source control is snappy and fast, it helps our developers focus longer and not have to be reacting to outages or waiting for things to happen.”
"It teaches them to organize their work so that their peers can read and contribute to it, and allows us to watch how they come together as a team and create workflows that fit their needs."
"We provide students with a cloud service, but they're responsible for deploying their projects."
"Actions is an exciting development and unlocks so much potential beyond CI/CD. It promises to streamline our workflows for a variety of tasks, from deploying our websites to querying the GitHub API for custom status reports to standard CI builds.”
"For open source projects, the lower the infrastructure friction we have, the easier it becomes to work with external contributors. Using GitHub Actions for CI and common tasks like triaging issues allows us to lower the barriers even more, so we can focus on writing a good product.”