Is Mergify down?

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.

Status: Identified 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. Affected components Workflow Automation & Merge Protections (Degraded performance) Merge Queue (Degraded performance)

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.

Status: Identified 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. Affected components Workflow Automation & Merge Protections (Degraded performance) Merge Queue (Degraded performance)

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.

Status: Monitoring 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. Affected components Workflow Automation & Merge Protections (Degraded performance) Merge Queue (Degraded performance)

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.

Status: Resolved 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. Affected components Workflow Automation & Merge Protections (Operational) Merge Queue (Operational)

Status: Resolved 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. Affected components Workflow Automation & Merge Protections (Operational) Merge Queue (Operational)

Status: Investigating Test results uploaded since 00:00 UTC today are not showing up in CI Insights and Test Engine. Uploads are being kept and will be processed once the issue is fixed. Merge queue and other Mergify features are not affected. We have identified where the failure comes from and are working on a fix. Affected components Test Engine (Degraded performance)

Test results uploaded since 00:00 UTC today are not showing up in CI Insights and Test Engine. Uploads are being kept and will be processed once the issue is fixed. Merge queue and other Mergify features are not affected. We have identified where the failure comes from and are working on a fix.

Status: Monitoring New test results are being processed again since 07:23 UTC, and CI Insights and Test Engine are catching up on uploads that were waiting. Test results uploaded between 00:00 and 07:23 UTC may still be missing. We kept those uploads and are working on reprocessing them, so they will show up later today. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected. Affected components Test Engine (Degraded performance)

New test results are being processed again since 07:23 UTC, and CI Insights and Test Engine are catching up on uploads that were waiting. Test results uploaded between 00:00 and 07:23 UTC may still be missing. We kept those uploads and are working on reprocessing them, so they will show up later today. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected.

Status: Monitoring We are now reprocessing the test results uploaded between 00:00 and 07:23 UTC. They will appear in CI Insights and Test Engine as the reprocessing goes through. New test results are still processed as usual. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected. Affected components Test Engine (Degraded performance)

We are now reprocessing the test results uploaded between 00:00 and 07:23 UTC. They will appear in CI Insights and Test Engine as the reprocessing goes through. New test results are still processed as usual. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected.

Status: Monitoring Reprocessing of the test results uploaded between 00:00 and 07:23 UTC is still in progress. Results from that window keep appearing in CI Insights and Test Engine as it goes through. New test results are processed as usual, and you do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected. Affected components Test Engine (Degraded performance)

Reprocessing of the test results uploaded between 00:00 and 07:23 UTC is still in progress. Results from that window keep appearing in CI Insights and Test Engine as it goes through. New test results are processed as usual, and you do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected.

Status: Resolved This incident is resolved. The test results uploaded between 00:00 and 07:23 UTC today have been reprocessed and are now available in CI Insights and Test Engine, and new results have been processed normally since 07:23 UTC. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected. We apologize for the delay in your test results. Affected components Test Engine (Operational)

Status: Resolved This incident is resolved. The test results uploaded between 00:00 and 07:23 UTC today have been reprocessed and are now available in CI Insights and Test Engine, and new results have been processed normally since 07:23 UTC. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected. We apologize for the delay in your test results. Affected components Test Engine (Operational)

This incident is resolved. The test results uploaded between 00:00 and 07:23 UTC today have been reprocessed and are now available in CI Insights and Test Engine, and new results have been processed normally since 07:23 UTC. You do not need to re-run your CI or re-upload anything. Merge queue and other Mergify features were not affected. We apologize for the delay in your test results.

Status: Monitoring Between 12:40 and 12:59 UTC, merge queues stopped starting new batches, so pull requests waiting in the queue did not progress. Processing resumed at 12:59 UTC, and the pull requests that were waiting have since been processed. No action is needed on your side: pull requests queued during that window continued on their own. We have identified the cause and are monitoring to confirm everything stays stable. Affected components Merge Queue (Operational)

Between 12:40 and 12:59 UTC, merge queues stopped starting new batches, so pull requests waiting in the queue did not progress. Processing resumed at 12:59 UTC, and the pull requests that were waiting have since been processed. No action is needed on your side: pull requests queued during that window continued on their own. We have identified the cause and are monitoring to confirm everything stays stable.

Status: Resolved This incident is resolved. We have since deployed a fix so the queue recovers from this kind of interruption on its own. Affected components Merge Queue (Operational)

Status: Resolved This incident is resolved. We have since deployed a fix so the queue recovers from this kind of interruption on its own. Affected components Merge Queue (Operational)

This incident is resolved. We have since deployed a fix so the queue recovers from this kind of interruption on its own.

Status: Investigating You may see this as Mergify not reacting to activity on your pull requests, so merge queues can stall and rules or checks may not update. The dashboard may fail to load, and API requests, including test result uploads from CI, may return errors. This causes delays, not incorrect merges: a pull request Mergify has not been able to fully evaluate is held rather than merged. Some activity during these periods may not have reached Mergify. Affected components GitHub Events Processing (Degraded performance) Merge Queue (Degraded performance)

You may see this as Mergify not reacting to activity on your pull requests, so merge queues can stall and rules or checks may not update. The dashboard may fail to load, and API requests, including test result uploads from CI, may return errors. This causes delays, not incorrect merges: a pull request Mergify has not been able to fully evaluate is held rather than merged. Some activity during these periods may not have reached Mergify.

Status: Resolved Issue is mitigated. If a pull request still looks stuck, comment "@mergifyio refresh" on it. Affected components GitHub Events Processing (Operational) Merge Queue (Operational)

Status: Resolved Issue is mitigated. If a pull request still looks stuck, comment "@mergifyio refresh" on it. Affected components GitHub Events Processing (Operational) Merge Queue (Operational)

Issue is mitigated. If a pull request still looks stuck, comment "@mergifyio refresh" on it.

Status: Investigating Our data processing infrastructure is running behind which is causing delays while ingesting test metrics. No data has been lost. Affected components GitHub Events Processing (Degraded performance)

Our data processing infrastructure is running behind which is causing delays while ingesting test metrics. No data has been lost.

Status: Identified We identified the issue and are working on a fix to release the congestion point. Affected components GitHub Events Processing (Degraded performance)

We identified the issue and are working on a fix to release the congestion point.

Status: Monitoring We have deployed a fix and test metrics processing has resumed. No data has been lost. Test results recorded throughout the incident were stored normally and will appear once processing catches up. Affected components GitHub Events Processing (Degraded performance)

We have deployed a fix and test metrics processing has resumed. No data has been lost. Test results recorded throughout the incident were stored normally and will appear once processing catches up.

Status: Resolved The issue has been fixed. Affected components GitHub Events Processing (Operational)

Status: Resolved The issue has been fixed. Affected components GitHub Events Processing (Operational)

The issue has been fixed.