GitHub Availability Report: April 2022
In April, we experienced three distinct incidents resulting in significant impact and degraded state of availability for Codespaces and GitHub Packages.
Category
In April, we experienced three distinct incidents resulting in significant impact and degraded state of availability for Codespaces and GitHub Packages.
This is the second and final post in a series describing friendly forks and alternative strategies for managing them.
Thanks to the efforts of the Elixir community, GitHub supports code navigation for Elixir repositories. Read how favorite language can add this support too!
This is the first post in a two-part series describing friendly forks and alternative strategies for managing them. Stay tuned for part two coming in May!
The history of pre-receive hooks, how we discovered that the performance was problematic, and how we went about safely replacing them.
We’re releasing exciting improvements that will streamline your Codespaces experience when working with multi-repository projects and monorepos.
Introducing CodeQL packs to help you codify and share your knowledge of vulnerabilities.
Another new release of Git is here! Take a look at some of our highlights on what's new in Git 2.36.
Upgrade your local installation of Git, especially if you are using Git for Windows, or you use Git on a multi-user machine.
How we sped up GitHub.com by moving slow, non-critical code into rack.after_reply.
Ensuring secure access to your source code is more important than ever. Git Credential Manager helps make that easy.
In March, we experienced several incidents resulting in significant impact to multiple GitHub services.
The new dependency review action and API prevents the introduction of known supply chain vulnerabilities into your code.
From automating builds and releases to taking care of large-scale regression testing, here are a few ways we use GitHub Actions to build GitHub.
We believe our technical interviews should be as similar as possible to the way we work at GitHub.
Over the past few weeks, we have experienced multiple incidents due to the health of our database. We wanted to share what we know about these incidents while our team continues to address them.