Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 11:11 UTC
Update - We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation. Nov 04, 2026 - 10:38 UTC
Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 04, 2026 - 09:53 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 09:50 UTC
Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests Nov 04, 2026 - 09:49 UTC
- access control (gitolite or similar) + key management (small webapp or api)
- branch protections, there's no prior art that I am aware of but hooks can be used for this)
- CI can be done by hooks as well, probably dispatching into a queue.
You don't really need PRs, agents can review the branch, humans review evidence. You probably don't need Wiki's or GH Pages or Discussions.You might use tickets, but they make cross repo planning and tracking difficult.
Hell, you probably don't need Confluence or Jira since docs and tickets should be in the repo itself (self contained state for agents). I am working on tooling for this... (an experiment!)
I've been relatively tolerant of the outages, but this is constant and really intolerable, to the point I'm actively migrating projects into our internal company GitLab.
I really hope they can sort their shit out.
Edit: while ! git push; do sleep 5; done