In 2012, HubSpot decided to simplify their development process in a way that consolidated the tools they were using, worked at scale as their headcount increased, and fit the company’s security requirements. But according to Tech Lead Mike Champion, the decision to switch to GitHub Enterprise ultimately came from HubSpot developers.
After three years using GitHub Enterprise, it has become deeply and broadly ingrained in HubSpot’s product teams—encompassing more than 1,000 repositories and over 1,500 deployable components. Here is how their team uses GitHub to securely communicate, recruit, and build software in the way that works best for them.
Pull requests are a central forum for conversation among HubSpot’s product team.They’re one of the main ways we communicate about ideas,
said Mike, GitHub has definitely become more than where we store code—it’s where we communicate about building software.
The conversation around HubSpot code is open and casual—often sprinkled with emoji—and rooted in the company’s feedback culture. Whether they are newly hired or have been around for years, HubSpot developers use GitHub to proactively seek out and receive feedback in informal channels. According to Mike, GitHub makes it easy for people to get feedback and comment on code across the company, no matter what project they are working on.
