ChangesGitHubIncident with Actions
GitHub: Critical incident: Incident with Actions
Summary pending. The diff below shows exactly what changed.
Discussed on Hacker News
- 16 points · 5 comments · posted · posted 22 min after the vendor’s first update
- 11 points · 1 comments · posted · posted 2 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Incident page: the full timeline of updates
What changed
Struck in red is what GitHub removed; blue is what they added. Muted text is unchanged context.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
After captured
In the 2026-11-09 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4d1021c89941a043…
History of this incident
Monday, November 9
5 incident changes
- Normal progressIncident
Incident updateIncident with Actions and Checks API
- Normal progressIncident
Incident updateIncident with Actions and Checks API
- Normal progressIncident
Incident updateIncident with Actions and Checks API
- Normal progressIncident
Incident updateIncident with Actions
- DegradationCritical incident
Incident with Actionsthis change
Cite this
Critical incident: Incident with Actions on GitHub’s status page, changed 2026-11-09 18:12 UTC (change 1 of 5).
- Title
- Critical incident: Incident with Actions
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/change/i8deaa49336f6cf