Always handle "completion/resolve" requests #4463
Open
Mergify / Summary
succeeded
Dec 10, 2024 in 1s
2 potential rules
Rule: Automatically update pull requests (update)
-
#commits-behind > 0
[📌 update requirement] -
label=merge me
-
-closed
[📌 update requirement] -
-conflict
[📌 update requirement] -
queue-position = -1
[📌 update requirement]
Rule: refactored queue action rule (queue)
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
label=merge me
-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#approved-reviews-by>=1
-
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success = docs/readthedocs.org:haskell-language-server
-
check-neutral = docs/readthedocs.org:haskell-language-server
-
check-skipped = docs/readthedocs.org:haskell-language-server
-
- any of: [🛡 GitHub branch protection]
-
check-success = test_post_job
-
check-neutral = test_post_job
-
check-skipped = test_post_job
-
- any of: [🛡 GitHub branch protection]
-
check-success = bench_post_job
-
check-neutral = bench_post_job
-
check-skipped = bench_post_job
-
- any of: [🛡 GitHub branch protection]
-
check-success = Hlint check run
-
check-neutral = Hlint check run
-
check-skipped = Hlint check run
-
- any of: [🛡 GitHub branch protection]
-
check-success = flags_post_job
-
check-neutral = flags_post_job
-
check-skipped = flags_post_job
-
- any of: [🛡 GitHub branch protection]
-
check-success = ci/circleci: stackage-nightly
-
check-neutral = ci/circleci: stackage-nightly
-
check-skipped = ci/circleci: stackage-nightly
-
-
- all of: [📌 queue conditions of queue
-
-closed
[📌 queue requirement] -
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
💖 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