Results of the GitHub Investigation
Last month, a number of allegations were made against GitHub and some of its employees, including one of its co-founders, Tom Preston-Werner. We took these claims seriously and launched a…

Last month, a number of allegations were made against GitHub and some of its employees, including one of its co-founders, Tom Preston-Werner. We took these claims seriously and launched a full, independent, third-party investigation.
The investigation found no evidence to support the claims against Tom and his wife of sexual or gender-based harassment or retaliation, or of a sexist or hostile work environment. However, while there may have been no legal wrongdoing, the investigator did find evidence of mistakes and errors of judgment. In light of these findings, Tom has submitted his resignation, which the company has accepted. Tom has been a huge part of this company from the very beginning and we appreciate all that he has done for GitHub. We wish him the best in his next endeavour.
As to the remaining allegations, the investigation found no evidence of gender-based discrimination, harassment, retaliation, or abuse.
We want to create a great place to work for all our employees and we can’t do that without acknowledging the challenges that exist in providing an inclusive work environment. We are implementing a number of new HR and employee-led initiatives as well as training opportunities to make sure employee concerns and conflicts are taken seriously and dealt with appropriately. We know we still have work to do.
Chris Wanstrath
CEO & Co-Founder
Written by
Related posts

Vibe coding with GitHub Copilot: Agent mode and MCP support rolling out to all VS Code users
In celebration of MSFT’s 50th anniversary, we’re rolling out Agent Mode with MCP support to all VS Code users. We are also announcing the new GitHub Copilot Pro+ plan w/ premium requests, the general availability of models from Anthropic, Google, and OpenAI, next edit suggestions for code completions & the Copilot code review agent.

GitHub Availability Report: February 2025
In February, we experienced two incidents that resulted in degraded performance across GitHub services.

GitHub Availability Report: January 2025
In January, we experienced two incidents that resulted in degraded performance across GitHub services.