{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidt4572rtxlkzlddipcau47ari7osocgzmtf53wz6vcbrrpipz5wm",
    "uri": "at://did:plc:cgr7sjkqpqcejzegy5n4x77g/app.bsky.feed.post/3mk7w4wzslov2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidytaiqqchnwy5hcxrzt26tzg6qfaksbrpeasuied4rvp7527nh4y"
    },
    "mimeType": "image/png",
    "size": 4268
  },
  "path": "/incidents/zsg1lk7w13cf",
  "publishedAt": "2026-04-23T21:43:26.000Z",
  "site": "https://www.githubstatus.com",
  "textContent": "Apr 23, 21:43 UTC\n**Resolved** - This incident has been resolved. We’ll share guidance for impacted organizations on how to remediate impacted branch state as soon as available.\n\nThank 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.\n\nApr 23, 21:18 UTC\n**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.\n\nThis behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.\n\nApr 23, 20:47 UTC\n**Update** - Pull Requests is operating normally.\n\nApr 23, 19:58 UTC\n**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.\n\nApr 23, 19:50 UTC\n**Investigating** - We are investigating reports of degraded performance for Pull Requests",
  "title": "Incident with Pull Requests",
  "updatedAt": "2026-04-24T00:23:20.000Z"
}