tests: fix relayer/consensus discrepancy for throttle v2 e2e test #1298
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Sep 14, 2023 in 1s
no rules match, no planned actions
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
6 not applicable rules
Rule: Backport patches to the release/v2.0.x branch (backport)
-
base=main -
label=A:backport/v2.0.x -
merged[:pushpin: backport requirement]
Rule: Backport patches to the release/v2.0.x-lsm branch (backport)
-
base=main -
label=A:backport/v2.0.x-lsm -
merged[:pushpin: backport requirement]
Rule: Backport patches to the release/v2.1.x-lsm branch (backport)
-
base=main -
label=A:backport/v2.1.x-lsm -
merged[:pushpin: backport requirement]
Rule: Backport patches to the release/v3.0.x branch (backport)
-
base=main -
label=A:backport/v3.0.x -
merged[:pushpin: backport requirement]
Rule: Backport patches to the release/v3.1.x branch (backport)
-
base=main -
label=A:backport/v3.1.x -
merged[:pushpin: backport requirement]
Rule: Backport patches to the release/v3.2.x-consumer branch (backport)
-
base=main -
label=A:backport/v3.2.x-consumer -
merged[:pushpin: backport requirement]
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
Loading