{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifbp654dmslkjpvuiian6aenrjzahzt4ujuna4oazzdh46q3j32fi",
    "uri": "at://did:plc:cgr7sjkqpqcejzegy5n4x77g/app.bsky.feed.post/3mjyepsvek2x2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidytaiqqchnwy5hcxrzt26tzg6qfaksbrpeasuied4rvp7527nh4y"
    },
    "mimeType": "image/png",
    "size": 4268
  },
  "path": "/incidents/m7pgzw1wlfq7",
  "publishedAt": "2026-04-21T05:04:56.000Z",
  "site": "https://www.githubstatus.com",
  "textContent": "Apr 21, 05:04 UTC\n**Resolved** - 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.\n\nApr 21, 04:18 UTC\n**Update** - The degradation has been mitigated. We are monitoring to ensure stability.\n\nApr 21, 03:10 UTC\n**Update** - The issue remains mitigated. Issues that were linked to projects during the incident may take approximately three more hours to render correctly while we complete a re-index.\n\nApr 20, 21:36 UTC\n**Update** - The degradation has been mitigated. We are monitoring to ensure stability.\n\nApr 20, 18:21 UTC\n**Update** - The degradation has been mitigated. We are monitoring to ensure stability.\n\nApr 20, 18:20 UTC\n**Monitoring** - The degradation has been mitigated. We are monitoring to ensure stability.\n\nApr 20, 18:20 UTC\n**Update** - The issue has been mitigated. Newly created issues linked to projects should now function as expected. Issues that were linked to projects during the incident may take approximately five hours to render correctly while we complete a re-index.\n\nApr 20, 18:08 UTC\n**Update** - A deployment to fix this issue of new issues not showing up in projects is underway.\n\nApr 20, 17:32 UTC\n**Update** - We continue to work on mitigation regarding new issues not showing on project boards.\n\nApr 20, 16:48 UTC\n**Update** - We continue to work on mitigation regarding new issues not showing on project boards.\n\nApr 20, 16:16 UTC\n**Update** - Code scanning default setup and Code Quality triggers are back up and running. PRs not processed before or during this incident will require a new push to trigger code scanning or code quality analysis.\n\nWe are seeing problems with new issues not showing on project boards and are working on mitigation.\n\nApr 20, 15:20 UTC\n**Update** - We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.\n\nApr 20, 14:38 UTC\n**Update** - We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.\n\nApr 20, 13:57 UTC\n**Update** - We are actively working to mitigate an issue affecting code scanning default setup and code quality features on pull requests. Users may experience pull request code scanning and code quality analyses not being triggered on new pull requests. Our engineering team has identified the root cause and working on mitigating the issue.\n\nApr 20, 13:28 UTC\n**Investigating** - We are investigating reports of impacted performance for some GitHub services.",
  "title": "Partial degradation for code scanning default setup and for code quality",
  "updatedAt": "2026-04-21T05:04:56.000Z"
}