Joining the White House in committing to tech inclusion
In May, we shared a report which measures our progress in the necessary work of diversifying our workforce. As we stated then, “we must create a company where anyone, regardless…
In May, we shared a report which measures our progress in the necessary work of diversifying our workforce. As we stated then, “we must create a company where anyone, regardless of what they look like or where they come from, can grow and thrive.” For GitHub to be the best version of itself, a diverse workforce is an imperative.
In the ongoing effort to make good on that promise, GitHub is joining our peers in the tech industry in signing the Tech Inclusion Pledge—an effort spearheaded by President Obama to “take action to make the technology workforce at each of our companies fully representative of the American people, as soon as possible.”
By signing this pledge, we are committing to:
- Implementing and publishing company-specific goals to recruit, retain, and advance diverse technology talent, and operationalize concrete measures to create and sustain an inclusive culture
- Annually publishing data and progress metrics on the diversity of our technology workforce across functional areas and seniority levels
- Investing in partnerships to build a diverse pipeline of technology talent to increase our ability to recognize, develop and support talent from all backgrounds.
As an industry, we will only be able to build products that change the world when we have more of the world at the table, engaged in their creation. We encourage our friends in tech to join in on this important pledge.
Written by
Related posts
Why developers still flock to Python: Guido van Rossum on readability, AI, and the future of programming
Discover how Python changed developer culture—and see why it keeps evolving.
Developers still need the right to challenge junk patents
Calling on developers, startups, and open source organizations to advocate against patent rules that would make it harder to challenge bad patents by the December 2 deadline.
GitHub Availability Report: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.