fix: delete already refunded fees from state if some fee cannot be refunded on channel closure #6255
Mergify / Summary
succeeded
May 7, 2024 in 4s
2 rules match and 10 potential rules
Rule: automerge to main with label automerge and branch protection passing (queue)
-
label=automerge
-
#approved-reviews-by>=1
-
-draft
[📌 queue requirement] -
base=main
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by>=2
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=build (amd64)
-
check-neutral=build (amd64)
-
check-skipped=build (amd64)
-
- any of: [🛡 GitHub branch protection]
-
check-success=build (arm)
-
check-neutral=build (arm)
-
check-skipped=build (arm)
-
- any of: [🛡 GitHub branch protection]
-
check-success=build (arm64)
-
check-neutral=build (arm64)
-
check-skipped=build (arm64)
-
- any of: [🛡 GitHub branch protection]
-
check-success=cleanup-runs
-
check-neutral=cleanup-runs
-
check-skipped=cleanup-runs
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (00)
-
check-neutral=tests (00)
-
check-skipped=tests (00)
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (01)
-
check-neutral=tests (01)
-
check-skipped=tests (01)
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (02)
-
check-neutral=tests (02)
-
check-skipped=tests (02)
-
- any of: [🛡 GitHub branch protection]
-
check-success=tests (03)
-
check-neutral=tests (03)
-
check-skipped=tests (03)
-
-
- all of: [📌 queue conditions of queue
Rule: backport patches to v1.0.x capability branch (backport)
-
label=backport-capability-to-v1.0.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v0.1.x callbacks ibc-go v7.3.x branch (backport)
-
label=backport-callbacks-to-v0.1.x+ibc-go-v7.3.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v0.2.x callbacks ibc-go v7.3.x branch (backport)
-
label=backport-callbacks-to-v0.2.x+ibc-go-v7.3.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v0.2.x callbacks ibc-go v8.0.x branch (backport)
-
label=backport-callbacks-to-v0.2.x+ibc-go-v8.0.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v0.1.x wasm ibc-go v7.3.x & wasmvm 1.5.x branch (backport)
-
label=backport-wasm-v0.1.x+ibc-go-v7.3.x-wasmvm-v1.5.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v0.1.x wasm ibc-go v8.0.x & wasmvm 1.5.x branch (backport)
-
label=backport-wasm-v0.1.x+ibc-go-v8.0.x-wasmvm-v1.5.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v0.2.x wasm ibc-go v8.3.x & wasmvm 2.0.x branch (backport)
-
label=backport-wasm-v0.2.x+ibc-go-v8.3.x-wasmvm-v2.0.x
-
base=main
-
merged
[📌 backport requirement]
Rule: backport patches to v7.4.x branch (backport)
-
label=backport-to-v7.4.x
-
base=main
-
merged
[📌 backport requirement]
✅ Rule: backport patches to v7.5.x branch (backport)
-
base=main
-
label=backport-to-v7.5.x
-
merged
[📌 backport requirement]
Rule: backport patches to v8.2.x branch (backport)
-
label=backport-to-v8.2.x
-
base=main
-
merged
[📌 backport requirement]
✅ Rule: backport patches to v8.3.x branch (backport)
-
base=main
-
label=backport-to-v8.3.x
-
merged
[📌 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