Add compliance test for sparse query parameters - #172
Draft
denisrosca wants to merge 4 commits into
Draft
denisrosca wants to merge 4 commits into
denisrosca wants to merge 4 commits into
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Sep 2, 2025 in 2s
no rules match, no planned actions
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
2 not applicable rules
Rule: Automatically approve/merge Scala Steward PRs on CI success (merge)
-
#commits-behind = 0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
author=scala-steward -
body~=labels:.*semver-spec-patch -
status-success="Build and Test" -
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
-closed[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: Automatically approve/merge Scala Steward PRs on CI success (review)
-
author=scala-steward -
body~=labels:.*semver-spec-patch -
status-success="Build and Test"
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