“Until now, team members almost never reviewed code or provided feedback, but since the introduction of GitHub, people started using pull requests to provide code reviews. Recently, there’s been feedback coming in from other teams as well, so we’re seeing collaboration across departments—that almost never happened before.”
“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.”
“We listen to the clinicians’ recommendations as we build the user interface to ensure we have the right features and functionality and the most comprehensive product going out to our customers."
"GitHub enables our developers to focus on what really matters. Shipping high-quality, secure code."
“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."
“Our engineers aren’t just building products, they’re building our customers’ futures."
“So we upgraded to GitHub Enterprise initially for the SAML support.”
“It’s more efficient for the developers, because you eliminate the need to learn a whole new set of tools if you move from one project or team to another.”
“It’s an agreement that a piece of code is stable, that it’s passed a certain set of evaluations, and is ready to move from one location to another.”
“And it turned out it was saved in Kafka.”
“Teams were more likely to use a piece of software from a third party than use code from the team across the hall.”
“GitHub opened all that up: workflows, pull requests, the whole thing.”
“Compared to other offerings, GitHub always has a head start and introduces bleeding edge features first. GitHub Actions, for example, is currently unparalleled by other vendors.”
“In my entire career, I’ve never had technical support as good as GitHub."