Feature suggestion — proactive notification for GitHub Actions incidents

[micheleoliveiracod]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Dear GitHub team,

I am writing as a frequent user of the platform to respectfully report a situation that caused me real harm. On 2026-07-19/20, during a confirmed GitHub Actions incident ("degraded availability... new workflows may delay or fail to start," per status.github.com), I pushed code for an academic project expecting my automated tests to run normally. Every run failed silently, with no indication that the cause was on the platform's side rather than my own code — I only learned the real reason afterward, by checking the status page myself, by which point there was no longer time to reorganize my testing plan.

I understand that instability is part of operating infrastructure at this scale. I would simply like to respectfully suggest that the team consider the possibility of a proactive, in-product notice (for example, a banner on the Actions tab) when there is a known, active incident affecting the service — today this information only reaches users who manually subscribe via email, SMS, Slack, or webhook through a separate system, which most users are unaware of.

Thank you very much for your attention, and I remain available for any further details. Request ID from the error received: E42C:183476:14FE625:18D56D0:6A5D647B.

Kind regards,
Michele Oliveira

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐