GitHub Merge Queue Silently Reverted Code During 4.5-Hour Incident — Squash/Rebase Configs Affected

GitHub Status / Hacker News·medium signal

GitHub disclosed that between April 23 16:05-20:43 UTC, a regression in merge queue caused PRs to be merged incorrectly when using squash merges or rebases. Some pull requests may have had code silently reverted during the window. GitHub identified the root cause and reverted the change. The same bug remained present in GitHub Enterprise Cloud with Data Residency, with the fix being rolled out separately. 57 points on HN.