At GitHub, we believe in empowering developers around the world. We also believe in basic human rights and treating people with respect and dignity. Today, I wanted to share a message I sent to all employees yesterday that is related to this, as it is important that we share our views on immigration policy with the world and not just internally with employees.

Software security is a collective problem, a responsibility that involves producers and consumers of code, open source maintainers, security researchers, and security teams. At GitHub, we want to give the community the tools it needs to secure the software we all depend on.

Today we’re announcing a big step in securing the open source supply chain: we’re welcoming Semmle to the GitHub family.

Sanctions impact both developers and the global open source community. Read more about how US trade sanctions affect GitHub—and how we’re advocating for as much access to code and collaboration as possible.

Since we introduced GitHub Actions last year, the response has been phenomenal, and developers have created thousands of inspired workflows. But we’ve also heard clear feedback from almost everyone: you want CI/CD! And that’s what we’re announcing today.

On Monday at 3:46 pm UTC, several services on GitHub.com experienced a 41-minute disruption, and as a result, some services were degraded for a longer period.

See how GitHub protects users against online censorship.

We’ve listened to your feedback about GitHub Package Registry and we’re changing the deletion policy for packages. Read more about the change and joining the beta.

We’ve acquired Pull Panda to help teams create more efficient and effective code review workflows on GitHub.

Software is truly changing the world, and I could not be more excited to be joining GitHub—the company at the center of it all—as Chief Operating Officer and help us scale to the next 36 million users and beyond.