← Back to GitHub History
minor✓ Resolved
Incident with Pull Requests
Status
resolved
Duration
1h 54m
Updates
4
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedThu, Apr 23, 2026, 09:45 PM
This incident has been resolved.
investigatingThu, Apr 23, 2026, 09:18 PM
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. <br /><br />This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
investigatingThu, Apr 23, 2026, 08:47 PM
Pull Requests is operating normally.
investigatingThu, Apr 23, 2026, 07:58 PM
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.
investigatingThu, Apr 23, 2026, 07:50 PM
We are investigating reports of degraded performance for Pull Requests
📊 TECHNICAL DETAILS
Internal ID
aee15dc4-2843-4174-86a8-dbbabcb154df
External ID
zsg1lk7w13cf
🕐 Started
Thu, Apr 23, 2026, 07:50 PM
🔄 Last Updated
Thu, Apr 23, 2026, 09:45 PM
✓ Resolved
Thu, Apr 23, 2026, 09:45 PM
MINOR
Impact Level
1h 54m
Total Duration
4
Status Updates
Affected Components
Pull Requests
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed