fix(ibc-hooks): safely construct JSON message using Go struct and json.Marshal - #278
Open
odaysec wants to merge 1 commit into
Open
fix(ibc-hooks): safely construct JSON message using Go struct and json.Marshal#278odaysec wants to merge 1 commit into
odaysec wants to merge 1 commit into
Mergify / Summary
succeeded
Nov 13, 2025 in 1s
1 potential rule
Rule: backport to maintained branches (backport)
-
label=BACKPORT -
merged[📌 backport requirement] -
base~=^(main|release/v7|release/v6)$
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
1 not applicable rule
Rule: automerge backported PR's for maintained branches (merge)
-
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
base~=^(release/v6|release/v7)$ -
branch-protection-review-decision = APPROVED[🛡 GitHub branch protection] -
label=automerge -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
#commits-behind = 0[🛡 GitHub branch protection] -
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
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