Skip to content

Follow up to the investigation results

Last Monday I published the least open and least transparent blog post GitHub has ever written.

We failed to admit and own up to our mistakes, and for that I'm sorry. GitHub has a reputation for being transparent and taking responsibility for our actions, but last week we did neither. There's no excuse. We can do a lot better.

I'd like to share with you as much as I can about what happened and a bit about how GitHub is changing.

When the allegations against GitHub were raised publicly we took them seriously and within days launched an investigation into what happened. We hired Rhoma Young, an independent, third-party investigator that GitHub had never worked with before. Rhoma has a long history of conducting fair and impartial investigations, with 30+ years of HR experience. She has worked with every type of organization, from Fortune 50 companies to local governments, and frequently testifies as an expert witness for both plaintiffs and defendants in depositions, arbitrations, and in litigation involving discrimination, harassment, retaliation, disability, and mitigation of damages.

Most importantly, Rhoma does not have a history of siding with companies or otherwise being a partisan, industry spokesperson. Half of her litigation witness work is on the side of employees, half for companies. Her job is to investigate situations and figure out what actually happened, even when the people who hired her don’t want to hear it.

We gave Rhoma free rein to review all the media reports, public allegations, and HR records so she could create her own investigation and interview plan. She identified three key issues that she focused her investigation on: the claims about Tom and his wife, the claims about the male engineer, and the general culture and working environment at GitHub.

Rhoma identified the employees she wanted to talk to based on an initial list we provided, the evidence she gathered, employees who asked to speak with her, people Julie asked her to speak with, and anyone else she determined was relevant, including Julie herself. Ultimately she conducted over 50 interviews during a four week period. Along with the interviews, Rhoma gathered and reviewed evidence consisting of emails, texts, transcripts, and code from the dozens of current and former GitHubbers she spoke with. She then took everything she learned and summarized her findings for GitHub's Board of Directors.

During the investigation, Rhoma promised participants confidentiality and we need to honor that promise. Rhoma’s report includes personal stories, private thoughts, documents, and all kinds of details that were shared for the purpose of the investigation, not for public consumption. We are trying to be transparent, but I hope you understand that there are privacy concerns preventing us from sharing the report in full. That said, I do want to provide more context for the findings we shared in last week’s blog post.

  • Founder allegations. The investigation found Tom Preston-Werner in his capacity as GitHub’s CEO acted inappropriately, including confrontational conduct, disregard of workplace complaints, insensitivity to the impact of his spouse's presence in the workplace, and failure to enforce an agreement that his spouse should not work in the office. There were also issues surrounding the solicitation of GitHub employees for non-GitHub business and the inappropriate handling of employee concerns regarding those solicitations.

    After being presented with the results we felt Tom could no longer be an effective leader at GitHub. He offered his resignation and we accepted.

  • Engineer allegations. The investigation found no information to support misconduct or opportunistic behavior by the engineer against Julie or any other female employees in the workplace. Furthermore, there was no information found to support Julie’s allegation that the engineer maliciously deleted her code. The commit history, push log, and all issues and pull requests involving Julie and the accused engineer were reviewed. The investigation considered all possible commits surrounding the accusation of passive-aggressive code removal. One instance was found where the engineer updated and broke some CSS in an internal application, which was fixed in a later commit. The investigator determined this change did not appear malicious.

  • GitHub’s working environment. Rhoma spent a significant amount of time investigating Julie’s claims of sexual and gender based harassment. After interviewing over 50 employees, former employees, and reviewing evidence, Rhoma found nothing to support a sexist or discriminatory environment at GitHub, and no information to suggest retaliation against Julie for making sex/gender harassment complaints. Employees were asked about their experiences here, good and bad. Women at GitHub reported feeling supported, mentored, and protected at work, and felt they are treated equitably and are provided opportunities.

Even so, we work in a world where inequality exists by default and we have to overcome that. Bullying, intimidation, and harassment, whether illegal or not, are absolutely unacceptable at GitHub and should not be tolerated anywhere. GitHub is committed to building a safe environment for female employees and all women in our community.

Our rapid growth left the leadership team, myself included, woefully unprepared to properly handle these types of situations. We're very aware this is a weakness, now more than ever, and it's naive to think we won't have these issues in the future. But learning how to properly handle conflict and building a safe working environment are two of our most important priorities.

I'm sorry to everyone we let down, including Julie. I realize this post doesn't fix or undo anything that happened. We're doing everything in our power to prevent it from happening again. Recently we hired an experienced head of HR and we clearly documented channels of communication that any GitHubber who needs support can use to make sure problems are dealt with effectively, but know we need to do more. In May we'll be sharing publicly the changes and the new initiatives we're launching. We love GitHub and we want it to be an inclusive and welcoming company worthy of the amazing people in our community and the amazing people that work here.

Thank you to all the GitHub employees, fans, and critics who gave us feedback this week. Your blog posts, tweets, and emails told us we could do better, and you were right.

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

OctoTales • UC Berkeley

Computer science professor, Armando Fox, is one of the thousands of teachers who use GitHub to give their students hands-on experience writing software in teams.

On a recent trip to UC Berkeley, we spoke with Armando and some of his students about open source, education, and the essential experience gained by building software for a real customer.

Teachers and students are eligible for free private repositories on GitHub. Learn more at education.github.com.

Update on Julie Horvath's Departure

This weekend, GitHub employee Julie Horvath spoke publicly about negative experiences she had at GitHub that contributed to her resignation. I am deeply saddened by these developments and want to comment on what GitHub is doing to address them.

We know we have to take action and have begun a full investigation. While that’s ongoing, and effective immediately, the relevant founder has been put on leave, as has the referenced GitHub engineer. The founder’s wife discussed in the media reports has never had hiring or firing power at GitHub and will no longer be permitted in the office.

GitHub has grown incredibly fast over the past two years, bringing a new set of challenges. Nearly a year ago we began a search for an experienced HR Lead and that person came on board in January 2014. We still have work to do. We know that. However, making sure GitHub employees are getting the right feedback and have a safe way to voice their concerns is a primary focus of the company.

As painful as this experience has been, I am super thankful to Julie for her contributions to GitHub. Her hard work building Passion Projects has made a huge positive impact on both GitHub and the tech community at large, and she's done a lot to help us become a more diverse company. I would like to personally apologize to Julie. It’s certain that there were things we could have done differently. We wish Julie well in her future endeavors.

Chris Wanstrath
CEO & Co-Founder

Behold: Image view modes

Now when you view commits that include images you'll be presented with four ways to view them: 2-up, Swipe, Onion Skin.

2-Up is the default mode, which lets you get a quick glimpse of both images. In addition, if the image has changed size between versions, the actual dimension change will be displayed. This should hopefully reduce headaches like shifts in UI alignment caused by asset size changes.

Swipe lets you view portions of your image side by side. Not sure if the colors shifted between versions? Drag the swipe slider over the area in question and compare the pixels for yourself.

Onion Skin really comes in handy when elements move around by small, hard to notice amounts. Did that icon shift two pixels to the left? Drag the opacity slider back a bit and see if things move around.

Difference is best used when it's not particularly obvious if something has changed. It will highlight only pixels that are different between the two images, making it the go-to view mode for finding those single pixel changes in a file.

All four modes are supported in the latest versions of the most common browsers. Versions of Internet Explorer before version 9 don't support canvas unfortunately, so Difference mode won't show up if you use those browsers.

I should also mention that the Difference mode is possible thanks to @Phrogz's awesome context-blender project that replicates Photoshop blend modes.

Want to try it for yourself? Check out the demo.

Random Repo

@joshthecoder said, "It’d be great to jump to a random repository on GitHub. Like the “Random article” feature on Wikipedia."

I said, “Yes, it would.”

Tada: Random Repository

Drag that link to your bookmark bar and have some fun.

Update: This feature has been retired.

Something went wrong with that request. Please try again.