Incident with Pull Requests

Apr 23, 21:43 UTC Resolved - This incident has been resolved. We’ll share guidance for impacted organizations on how to remediate impacted branch state as soon as available.

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.

Apr 23, 21:18 UTC Update - 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.

Apr 23, 20:47 UTC Update - Pull Requests is operating normally.

Apr 23, 19:58 UTC Update - 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.

Apr 23, 19:50 UTC Investigating - We are investigating reports of degraded performance for Pull Requests