mv: handle different ERMs for base and view table #18816
Closed
Mergify / Summary
succeeded
May 28, 2024 in 2s
3 rules match
✅ Rule: Automate backport pull request 5.2 (copy)
-
label=backport/5.2 -
label=promoted-to-master - any of:
-
closed -
merged
-
- any of:
-
base=master -
base=next
-
✅ Rule: Automate backport pull request 5.4 (copy)
-
label=backport/5.4 -
label=promoted-to-master - any of:
-
closed -
merged
-
- any of:
-
base=master -
base=next
-
✅ Rule: Automate backport pull request 6.0 (copy)
-
label=backport/6.0 -
label=promoted-to-master - any of:
-
closed -
merged
-
- any of:
-
base=master -
base=next
-
2 not applicable rules
Rule: put PR in draft if conflicts (edit)
-
author = mergify[bot] -
head ~= ^mergify/ -
label = conflicts
Rule: Delete mergify backport branch (delete_head_branch)
-
base~=branch- -
closed[📌 delete_head_branch requirement] - any of:
-
closed -
merged
-
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branch
Additionally, on Mergify dashboard you can:
- look at your merge queues
- generate the Mergify configuration with the config editor.
Finally, you can contact us on https://mergify.com