Live / Mergify / Incident
Mergify: Some pull requests wrongly asked to be rebased manually
Mergify · mergify.comMinor incidentResolved2026-10-28 17:41 UTC
Public — what happened
Summary
Mergify said some pull requests that use the rebase merge method were wrongly refused by its merge queue or merge action with a message saying a manual rebase was needed, even though they had no conflicts. The company said this began October 26 and that a first fix deployed on October 27 stopped affected requests from being removed from the queue, leaving only a few still refused by October 28. Mergify said the cause was a change in how GitHub reports whether a pull request can be rebased, which it was raising with GitHub while preparing its own fallback fix. It offered a workaround of re-triggering the affected rule, such as by removing and re-adding a label, and the incident is marked resolved as of October 28 at 17:41 UTC.
Timeline
- Started — 2026-10-27 18:27 UTC
- Identified — 2026-10-27 18:27 UTC (2 updates)
- Monitoring — 2026-10-28 15:28 UTC
- Resolved — 2026-10-28 17:41 UTC · 23h 14m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Mergify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Mergify: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Mergify report →
More from Mergify
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.