Resolved on April 23, 2026, affecting Pull Requests.
This incident has been resolved and we've contacted repository administrators via email who have impacted branches. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will also be shared as soon as it is available.
Affected components
Update timeline
- investigating Apr 23, 2026, 07:50 PM UTC
We are investigating reports of degraded performance for Pull Requests
- investigating Apr 23, 2026, 07:58 PM UTC
We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.
- investigating Apr 23, 2026, 08:47 PM UTC
Pull Requests is operating normally.
- investigating Apr 23, 2026, 09:18 PM UTC
We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC. This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
- resolved Apr 23, 2026, 09:43 PM UTC
This incident has been resolved and we've contacted repository administrators via email who have impacted branches. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will also be shared as soon as it is available.
Your product runs on more than GitHub
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services