New ship: 🟢 GitHub Incident Updates

[tuves]

At GitHub we pride ourselves in how we communicate effectively across time zones, teams, tools, and of course to our customers. We understand that no product is perfect, and there will be times when there are unsuspected degradations or outages. But in keeping true to our aim to make information as open and accessible as possible, we will now be posting updates and status interruptions in real-time here in the community.

This will give you a centralized thread in Community Discussions for you to share your experiences and find up to date information as it impacts your work.

What Can You Expect?

• If an incident occurs and is on our GitHub status page, a discussion will post declaring the incident in the community
• The ability to subscribe to open discussion for real-time updates
• Subsequent updates to post on the incident’s discussion thread
• Declaration of the incident resolving, you will see a marked answer and an image indicating the incident is resolved
• If available: a link to the public incident summary

Thank you for your patience as we launch this and work out possible kinks!

[Andre601]

Would it be possible to maybe have a dedicated repository for this, so that one can subscribe to any activity there?
I would love to follow incidents here, but I simply cannot check the community discussion frequently to find and subscribe to incident-related discussions.

One alternative would imo be to have issues enabled, as that would be a different medium to subscribe to and get notified about.
Tho, it has the issues (no pun intended) to have people spam issues, unless you block creation via issue-template chooser, while allowing github-actions (or whatever account posts here) to make new ones...

It's... difficult, now that I think about it. But a dedicated repository would imo be a bit better here...

[tuves]

Hi @Andre601,

Thank you for the feedback--I'll pass it along to the teams to discuss. For additional context, the reason we wanted to post updates here in real time was for community members who often open new discussions when they've run into a degradation or outage. This can lead to many splintered conversations, many which cannot be answered or acknowledged by our dedicated staff. Even though updates will be provided in real time here, they will also be posted in GitHub Status, which you can subscribe to. Another option is to filter your discussions view by labels, and only viewing "incident" ones.

Essentially, for those who are already here, we want to make the information easier to access and engage with.