“And it turned out it was saved in Kafka.”

“With GitHub Actions, we don’t have to think about the hidden costs of maintaining the CI/CD servers. The workflows are so smooth that the automation works as it should, so developers can focus on communicating with customers and developing new innovations.”

“We get everything we need from the GitHub Actions marketplace to build and support our tailored CI/CD pipeline.”

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

“We use GitHub as a community management system–kind of like a social network."

“Just by being open source and publicly visible on GitHub, we have developers who directly contact us with bugs.”

“We leverage quite a lot of community input to design the roadmap."

“When I came onboard we were dealing with a heterogeneous development landscape, where everyone had to be a DevOps engineer to get anything built or published."

"We now see other teams contributing to these pipelines and workflows."

“Some parts of the business need to be deploying software changes multiple times a day to stay current."

“It fits in well with our CI/CD process because Dependabot follows the same rules our developers follow.”

“With GitHub, there is a radical difference in how we use the tool.”

"GitHub was phenomenal. They supported us in the business case versus rushing us into the enterprise license before we had proven it. That was a key enabler for us.”

“GitHub became the platform to bring all these teams together.”

“GitHub gives us the controls and oversight we need without placing a burden on our developers or hampering their ability to innovate."