Scenario long-tail: GitHub pull request merge times out during a frontend release - how to verify merge state and handoff.
GitHub recorded an incident on November 16, 2026 affecting Pull Requests and Actions workflow starts. The official status record reported elevated pull request merge timeouts of roughly 2-3 percent against a baseline near 0.2 percent. The incident was resolved after the recorded window.
Preserve the merge decision
When a merge fails or times out, capture the repository, pull request number, commit SHA, check state, UTC timestamp and exact UI or API error. Do not repeatedly click merge without recording whether the request created a merge commit or changed the pull request timeline.
The first question is whether the repository timeline shows a completed merge, a new attempt or no state change. The second is whether required checks completed independently. This prevents duplicate releases and avoids telling a client that a code change was lost when the merge completed after a delay.
Use a safe retry path
After the provider marks the incident resolved, retry once from the recorded pull request state. Re-check the head SHA, merge status and required checks. If the same request fails, move to an operator handoff with the captured evidence rather than changing branch protection or bypassing required review.
Merge handoff record
Use four rows: observed merge request, repository timeline, required-check state and client release decision. The release owner can then choose retry, wait, manual review or a separately approved repository change.
Applicability and limits
This applies to GitHub repositories that use pull request merges during the incident window or a similar provider-side degradation. It does not establish a client outage, a code defect or a need to disable protections. GitHub status is an incident source, not a substitute for repository evidence. No repository timeline or merge attempt was inspected for this article.