Fix PFM to not fail packets that aren't FungibleTokenPacketData
#105
Mergify / Summary
succeeded
Sep 28, 2023 in 6s
1 rule matches
Rule: backport to maintained branches (backport)
-
base~=^(main|release/v4|release/v5|release/v6)$ -
label=BACKPORT -
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!
1 not applicable rule
Rule: automerge backported PR's for maintained branches (merge)
-
base~=^(release/v4|release/v5|release/v6)$ -
label=automerge -
#approved-reviews-by>=1[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0[🛡 GitHub branch protection] -
#commits-behind=0[🛡 GitHub branch protection] -
-draft[:pushpin: merge requirement] -
-mergify-configuration-changed[:pushpin: merge -> allow_merging_configuration_change setting requirement] -
branch-protection-review-decision=APPROVED[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=Linter (./modules/async-icq) -
check-neutral=Linter (./modules/async-icq) -
check-skipped=Linter (./modules/async-icq)
-
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