GitHub Outage Affecting Builds and Push to Deploy

This incident has been resolved. GitHub has restored the affected services on their end, and builds and Push to Deploy deployments on Galaxy are operating normally. If a deploy failed during the outage, or if a commit didn't trigger a Push to Deploy build, you can trigger it again and it should now complete as expected. We apologize for the disruption and thank you for your patience.

We are currently experiencing issues due to an ongoing GitHub outage.

GitHub has reported degraded availability across multiple services, including archive downloads and raw repository content, which are currently returning errors at an elevated rate.

During builds, you may encounter errors while dependencies are installed. As a result, your build may fail intermittently. Deployments triggered by Push to Deploy may also fail to start, since new commits reach Galaxy through GitHub webhooks, which are degraded in the same incident.

Retrying a deploy may succeed, though failures are likely to continue while the outage is ongoing. This is not caused by any change on Galaxy's infrastructure, and the affected operations will resume automatically once GitHub recovers.

We are actively monitoring GitHub's status and will provide updates as necessary. You can follow their updates here: https://www.githubstatus.com