From b4200fac4cecc9d22ce5143c1d9f718c108ffcbc Mon Sep 17 00:00:00 2001 From: Miguel Palazzo <50017+miguelpalazzo@users.noreply.github.com> Date: Tue, 1 Oct 2024 13:32:54 -0400 Subject: [PATCH 1/2] Add GitHub's missing incident reports for 2023 --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 97d41ca..ab87543 100644 --- a/README.md +++ b/README.md @@ -430,6 +430,10 @@ Numerous organizations frequently share their insights and expertise, encompassi ### Major incidents & analysis reports +* [GitHub Availability Report: December 2023](https://github.blog/news-insights/company-news/github-availability-report-december-2023/) +* [GitHub Availability Report: November 2023](https://github.blog/news-insights/company-news/github-availability-report-november-2023/) +* [GitHub Availability Report: October 2023](https://github.blog/news-insights/company-news/github-availability-report-october-2023/) +* [GitHub Availability Report: September 2023](https://github.blog/news-insights/company-news/github-availability-report-september-2023/) * [GitHub Availability Report: August 2023](https://github.blog/2023-09-13-github-availability-report-august-2023/) * [GitHub Availability Report: July 2023](https://github.blog/2023-08-09-github-availability-report-july-2023/) * [GitHub Availability Report: June 2023](https://github.blog/2023-07-12-github-availability-report-june-2023/) From 7752e6c496bfc0866dfd2c3031bbe51ee684ec3c Mon Sep 17 00:00:00 2001 From: Miguel Palazzo <50017+miguelpalazzo@users.noreply.github.com> Date: Tue, 1 Oct 2024 13:34:15 -0400 Subject: [PATCH 2/2] Add GitHub's incident reports for 2024 --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index ab87543..6ff84c8 100644 --- a/README.md +++ b/README.md @@ -430,6 +430,14 @@ Numerous organizations frequently share their insights and expertise, encompassi ### Major incidents & analysis reports +* [GitHub Availability Report: August 2024](https://github.blog/news-insights/company-news/github-availability-report-august-2024/) +* [GitHub Availability Report: July 2024](https://github.blog/news-insights/company-news/github-availability-report-july-2024/) +* [GitHub Availability Report: June 2024](https://github.blog/news-insights/company-news/github-availability-report-june-2024/) +* [GitHub Availability Report: May 2024](https://github.blog/news-insights/company-news/github-availability-report-may-2024/) +* [GitHub Availability Report: April 2024](https://github.blog/news-insights/company-news/github-availability-report-april-2024/) +* [GitHub Availability Report: March 2024](https://github.blog/news-insights/company-news/github-availability-report-march-2024/) +* [GitHub Availability Report: February 2024](https://github.blog/news-insights/company-news/github-availability-report-february-2024/) +* [GitHub Availability Report: January 2024](https://github.blog/news-insights/company-news/github-availability-report-january-2024/) * [GitHub Availability Report: December 2023](https://github.blog/news-insights/company-news/github-availability-report-december-2023/) * [GitHub Availability Report: November 2023](https://github.blog/news-insights/company-news/github-availability-report-november-2023/) * [GitHub Availability Report: October 2023](https://github.blog/news-insights/company-news/github-availability-report-october-2023/)