You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On backport, a single branch should be created, and the Mergify bot should open a single PR from it to the target branch.
Actual Behavior
I've just had an example where Mergify created a single branch, but then opened two separate PRs from it to the same target branch. (I didn't even know that was possible on GitHub - it's possible it's a GH bug and not a mergify one.)
Steps to Reproduce the Problem
I'm not sure - it's just happened once, with no changes to the Mergify configuration since the last successful action (a couple of hours prior to the "failure").
Thanks for reporting the issue. We've looked into that.
It turns out Mergify did everything right, but the first backport PR request has timed out. Mergify considered this as "not working" and retried a few seconds later the same request, which created the "real" backport as far as Mergify is concerned.
Expected Behavior
On backport, a single branch should be created, and the Mergify bot should open a single PR from it to the target branch.
Actual Behavior
I've just had an example where Mergify created a single branch, but then opened two separate PRs from it to the same target branch. (I didn't even know that was possible on GitHub - it's possible it's a GH bug and not a mergify one.)
Steps to Reproduce the Problem
I'm not sure - it's just happened once, with no changes to the Mergify configuration since the last successful action (a couple of hours prior to the "failure").
Specifications
The text was updated successfully, but these errors were encountered: