-
“Our engineers aren’t just building products, they’re building our customers’ futures."
-
“That’s why we’ve been conducting usability studies, we want developers to be able to complete their workflows as fast as possible.”
-
“We want to make sure that people at Meta who are responsible for maintaining these projects can see the data and information they need to keep projects going.”
-
"The GitHub team was very responsive and quick to provide a tool for migrating our projects."
-
“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."
-
"I wanted a flexible platform I could automate against. Being able to build on top of GitHub is a very big benefit."
-
“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 clearly needed to find a solution."
-
"There’s never been a moment where we considered moving off GitHub. That’s radical for a piece of software we’ve used for over nine years."
-
“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."
-
“We have one of the biggest monolithic Ruby on Rails applications in the world, and it’s hosted in a single GitHub repository."
-
“This year, our production applications changed more than 50 times a day, and it’s changing even faster now. GitHub helps us meet this demand.”