Some pull requests wrongly asked to be rebased manually

Update timeline

1. identified Oct 27, 2026, 06:27 PM UTC

   Since October 26, some pull requests using the rebase merge method are refused by the merge queue or by the merge action with the message "Pull request must be rebased manually", even though they have no conflict. We have deployed a first fix: pull requests are no longer removed from the queue when the base branch moves. Until the remaining part is fixed, an affected pull request can be unblocked by re-triggering the rule that queues or merges it, for example by removing and re-adding its queue label. If the rule isn't triggered by a label, add or remove any label on the pull request, then comment "@Mergifyio refresh". Next update by 09:00 UTC tomorrow.

2. identified Oct 27, 2026, 06:27 PM UTC

   Since October 26, some pull requests using the rebase merge method are refused by the merge queue or by the merge action with the message "Pull request must be rebased manually", even though they have no conflict. We have deployed a first fix: pull requests are no longer removed from the queue when the base branch moves. Until the remaining part is fixed, an affected pull request can be unblocked by re-triggering the rule that queues or merges it, for example by removing and re-adding its queue label. If the rule isn't triggered by a label, add or remove any label on the pull request, then comment "@Mergifyio refresh". Next update by 09:00 UTC tomorrow.

3. identified Oct 28, 2026, 09:29 AM UTC

   Some pull requests using the rebase merge method are still refused with "Pull request must be rebased manually" although they have no conflict. This comes from a change in GitHub's behavior: right after a commit lands on the base branch, GitHub can report pull requests as not rebaseable for a while, even when they rebase cleanly, and Mergify relies on that information. We are in contact with GitHub about it, and we are preparing a best-effort fix on our side in case GitHub does not correct it. In the meantime, an affected pull request can be unblocked by re-triggering the rule that queues or merges it, for example by removing and re-adding its queue label. If the rule isn't triggered by a label, add or remove any label on the pull request, then comment "@Mergifyio refresh". Next update by 16:00 UTC.

4. identified Oct 28, 2026, 09:29 AM UTC

   Some pull requests using the rebase merge method are still refused with "Pull request must be rebased manually" although they have no conflict. This comes from a change in GitHub's behavior: right after a commit lands on the base branch, GitHub can report pull requests as not rebaseable for a while, even when they rebase cleanly, and Mergify relies on that information. We are in contact with GitHub about it, and we are preparing a best-effort fix on our side in case GitHub does not correct it. In the meantime, an affected pull request can be unblocked by re-triggering the rule that queues or merges it, for example by removing and re-adding its queue label. If the rule isn't triggered by a label, add or remove any label on the pull request, then comment "@Mergifyio refresh". Next update by 16:00 UTC.

5. monitoring Oct 28, 2026, 03:28 PM UTC

   Since our first fix yesterday at 16:53 UTC, most pull requests are no longer affected: only a few have been wrongly refused today. The cause is still a change in GitHub's behavior, which GitHub has not corrected yet, so we are keeping this incident open and are still preparing a best-effort fix on our side in case they don't. A pull request refused earlier stays blocked until its rule runs again. Removing and re-adding its queue label does it. If the rule isn't triggered by a label, add or remove any label on the pull request, then comment "@Mergifyio refresh". Next update by 09:00 UTC tomorrow.

6. monitoring Oct 28, 2026, 03:28 PM UTC

   Since our first fix yesterday at 16:53 UTC, most pull requests are no longer affected: only a few have been wrongly refused today. The cause is still a change in GitHub's behavior, which GitHub has not corrected yet, so we are keeping this incident open and are still preparing a best-effort fix on our side in case they don't. A pull request refused earlier stays blocked until its rule runs again. Removing and re-adding its queue label does it. If the rule isn't triggered by a label, add or remove any label on the pull request, then comment "@Mergifyio refresh". Next update by 09:00 UTC tomorrow.

7. resolved Oct 28, 2026, 05:41 PM UTC

   This incident is resolved. We released a fix, and since 17:15 UTC pull requests that rebase cleanly are no longer asked to be rebased manually. A pull request refused before 17:15 UTC stays blocked until its rule runs again: remove and re-add its queue label, or comment "@Mergifyio refresh" on it.

8. resolved Oct 28, 2026, 05:41 PM UTC

   This incident is resolved. We released a fix, and since 17:15 UTC pull requests that rebase cleanly are no longer asked to be rebased manually. A pull request refused before 17:15 UTC stays blocked until its rule runs again: remove and re-add its queue label, or comment "@Mergifyio refresh" on it.

9. resolved Oct 28, 2026, 05:41 PM UTC

   This incident is resolved. We released a fix, and since 17:15 UTC pull requests that rebase cleanly are no longer asked to be rebased manually. A pull request refused before 17:15 UTC stays blocked until its rule runs again: remove and re-add its queue label, or comment "@Mergifyio refresh" on it.