GitHub experienced a regression in merge queue functionality that caused pull requests to be merged incorrectly when using squash merges or rebases between 16:05-20:43 UTC. The issue affected GitHub's Pull Requests service for 1.9 hours before being resolved by reverting the problematic change. Users who utilized merge queue with squash or rebase configurations may have had their pull requests processed incorrectly during this timeframe.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
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.
Pull Requests is operating normally.
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.
We are investigating reports of degraded performance for Pull Requests
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with