fix(multi-networks): configure scylla correctly with the right interface #9500
Mergify / Summary
succeeded
Dec 10, 2024 in 0s
9 potential rules
Rule: Automate backport pull request 6.0 (backport)
-
label=backport/6.0
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request 6.1 (backport)
-
label=backport/6.1
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request 6.2 (backport)
-
label=backport/6.2
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request 2023.1 (backport)
-
label=backport/2023.1
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request 2024.1 (backport)
-
label=backport/2024.1
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request 2024.2 (backport)
-
label=backport/2024.2
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request perf-v14 (backport)
-
label=backport/perf-v14
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request perf-v15 (backport)
-
label=backport/perf-v15
-
merged
[📌 backport requirement] -
base=master
Rule: Automate backport pull request perf-v16 (backport)
-
label=backport/perf-v16
-
merged
[📌 backport requirement] -
base=master
1 not applicable rule
Rule: put PR in draft if conflicts (edit)
-
author = mergify[bot]
-
label = conflicts
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 refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will 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
Loading