Why we’re excited about the Sigstore general availability
The Sigstore GA means you can protect your software supply chain today with GitHub Actions, and will power new npm security capabilities in the near future.
The Sigstore GA means you can protect your software supply chain today with GitHub Actions, and will power new npm security capabilities in the near future.
In September, we experienced one incident that resulted in degraded performance across GitHub services. We also experienced one incident resulting in significant impact to Codespaces. We are still investigating that incident and will include it in next month’s report. This report also sheds light into an incident that impacted Codespaces in August and an incident that impacted Actions in August.
Access to the open internet is essential to defending human rights, and developers have an important role in promoting freedom of expression and transparency. GitHub is committed to keeping Iranians connected to the global developer community.
In August, we experienced one incident resulting in significant impact to Codespaces. We’re still investigating that incident and will include it in next month’s report. This report also sheds light into an incident that impacted Codespaces in July.
In July, we experienced one incident that resulted in degraded performance for Codespaces. This report also acknowledges two incidents that impacted multiple GitHub.com services in June.
Enhanced Two-Factor Authentication (2FA) experience is now Generally Available. Previously, we had announced a set of improvements in our public beta. Further to this we have made the following new…
In June, we experienced four incidents resulting in significant impact to multiple GitHub.com services. This report also sheds light into an incident that impacted several GitHub.com services in May.
In May, we experienced three distinct incidents resulting in significant impact to multiple services across GitHub.com. This report also sheds light into the billing incident that impacted Actions and Codespaces users in April.
In April, we experienced three distinct incidents resulting in significant impact and degraded state of availability for Codespaces and GitHub Packages.
In March, we experienced several incidents resulting in significant impact to multiple GitHub services.
In February, we experienced one incident resulting in significant impact to multiple GitHub services.
In January, we experienced no incidents resulting in service downtime to our core services.
In December, we experienced no incidents resulting in service downtime to our core services.
In November, we experienced one incident resulting in significant impact and degraded state of availability for multiple services.
In October, we experienced one incident resulting in significant impact and degraded state of availability for the GitHub Codespaces service.
In September, we experienced no incidents resulting in service downtime to our core services.
In August, we experienced two distinct incidents resulting in significant impact and degraded state of availability for Git operations, API requests, webhooks, issues, pull requests, GitHub Pages, GitHub Packages, and GitHub Actions services.
Maintainers can now manage the repository-level “Allow auto-merge” setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only admins…
In July, GitHub experienced no incidents resulting in service downtime to our core services.
In June, we experienced no incidents resulting in service downtime to our core services.
In May, we experienced two incidents resulting in significant impact to multiple GitHub services.
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Catch up on the GitHub podcast, a show dedicated to the topics, trends, stories and culture in and around the open source developer community on GitHub.