feat!: provider proposal for changing reward denoms #1280
Merged
Mergify / Summary
succeeded
Nov 13, 2023 in 3s
2 rules match and 4 potential rules
Rule: Backport patches to the release/v2.0.x branch (backport)
-
label=A:backport/v2.0.x
-
base=main
-
merged
[:pushpin: backport requirement]
Rule: Backport patches to the release/v2.0.x-lsm branch (backport)
-
label=A:backport/v2.0.x-lsm
-
base=main
-
merged
[:pushpin: backport requirement]
Rule: Backport patches to the release/v2.1.x-provider-lsm branch (backport)
-
base=main
-
label=A:backport/v2.1.x-provider-lsm
-
merged
[:pushpin: backport requirement]
Rule: Backport patches to the release/v3.0.x branch (backport)
-
label=A:backport/v3.0.x
-
base=main
-
merged
[:pushpin: backport requirement]
Rule: Backport patches to the release/v3.1.x branch (backport)
-
label=A:backport/v3.1.x
-
base=main
-
merged
[:pushpin: backport requirement]
Rule: Backport patches to the release/v3.2.x branch (backport)
-
base=main
-
label=A:backport/v3.2.x
-
merged
[:pushpin: backport requirement]
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
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