GitHub’s Engineering Team has moved to Codespaces
Over the past months, we’ve left our macOS model behind and moved to Codespaces for the majority of GitHub.com development.
Over the past months, we’ve left our macOS model behind and moved to Codespaces for the majority of GitHub.com development.
In July, GitHub experienced no incidents resulting in service downtime to our core services.
At GitHub, we recently added a new feature to Rails that will be available in 7.0: support for handling associations across database clusters.
In June, we experienced no incidents resulting in service downtime to our core services.
We recently set about creating a framework and service for automatically generating social sharing images for repositories and other resources on GitHub.
In May, we experienced two incidents resulting in significant impact to multiple GitHub services.
Over the years, GitHub engineers have developed many ways to observe how our systems behave. We mostly make use of statsd for metrics, the syslog format for plain text logs and OpenTracing for request traces.
GitHub is the home for software development teams and is the place where they collaborate and build. For larger organizations, you might have a dedicated reporting team that wants to export this activity at a
GitHub has been at the forefront of security key adoption for many years. We were an early adopter of Universal 2nd Factor (“U2F”) and were also one of the first sites to transition to Webauthn.
In April, we experienced two incidents resulting in significant impact and degraded state of availability for API requests and the GitHub Packages service, specifically the GitHub Packages Container registry service. April 1 21:30 UTC (lasting