Fix neo-swaps doc strings #1250
Merged
Mergify / Summary
succeeded
Feb 9, 2024 in 12s
6 potential rules
Rule: Auto merge (queue)
-
check-success=Checks (parachain)
-
check-success=Quick check benchmarks
-
check-success=Test parachain build
-
#approved-reviews-by>=1
-
#changes-requested-reviews-by=0
-
-draft
[📌 queue requirement] -
check-success=Checks (clippy)
-
check-success=Checks (standalone)
-
check-success=Copyright Notices
-
check-success=Coverage
-
check-success=Format
-
check-success=Fuzz
-
check-success=Test standalone build
-
label=s:accepted
- 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>=1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection]
-
- all of: [📌 queue conditions of queue
Rule: Auto merge (label)
-
check-success=Checks (parachain)
-
check-success=Quick check benchmarks
-
check-success=Test parachain build
-
#approved-reviews-by>=1
-
#changes-requested-reviews-by=0
-
check-success=Checks (clippy)
-
check-success=Checks (standalone)
-
check-success=Copyright Notices
-
check-success=Coverage
-
check-success=Format
-
check-success=Fuzz
-
check-success=Test standalone build
-
label=s:accepted
Rule: ask to resolve conflict (comment, label)
-
conflict
Rule: Set in-progress label after changes are pushed (label)
-
commits[-1].date_committer>=0 days 00:01 ago
-
commits[-1].author!=mergify[bot]
Rule: Trigger CI after Mergify merged the base branch (fix merge queue) (label)
-
commits[-1].author=mergify[bot]
-
commits[-1].date_committer>=0 days 00:01 ago
-
queue-position=0
Rule: Remove CI trigger label (label)
-
commits[-1].author=mergify[bot]
-
label=s:review-needed
-
queue-position=0
💖 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