Bump prospector from 1.11.0 to 1.13.3 in /requirements #1725
Mergify / Summary
succeeded
Nov 19, 2024 in 1s
4 potential rules
The configuration uses the deprecated
merge_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
Rule: Dependency updater - automatic merge on CI passing (delete_head_branch)
-
closed
[📌 delete_head_branch requirement] -
status-success=test (3.x, 12, lint)
-
status-success=test (3.x, 12, py3-cov)
-
-merged
-
author~=^(pyup-bot|dependabot\[bot\])$
Rule: Dependency updater - automatic merge on CI passing (queue)
-
status-success=test (3.x, 12, lint)
-
status-success=test (3.x, 12, py3-cov)
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-neutral = test (3.x, 12, lint)
-
check-skipped = test (3.x, 12, lint)
-
check-success = test (3.x, 12, lint)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = test (3.x, 12, py3-cov)
-
check-skipped = test (3.x, 12, py3-cov)
-
check-success = test (3.x, 12, py3-cov)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
-
-closed
[📌 queue requirement] -
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
-merged
-
author~=^(pyup-bot|dependabot\[bot\])$
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
Rule: Automatic merge on approval (delete_head_branch)
-
#approved-reviews-by>=1
-
closed
[📌 delete_head_branch requirement] -
label=ready to merge
-
#changes-requested-reviews-by=0
Rule: Automatic merge on approval (queue)
-
#approved-reviews-by>=1
-
label=ready to merge
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]- any of: [🛡 GitHub branch protection]
-
check-neutral = test (3.x, 12, lint)
-
check-skipped = test (3.x, 12, lint)
-
check-success = test (3.x, 12, lint)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = test (3.x, 12, py3-cov)
-
check-skipped = test (3.x, 12, py3-cov)
-
check-success = test (3.x, 12, py3-cov)
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
-
#changes-requested-reviews-by=0
-
-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!
2 not applicable rules
Rule: Dependency updater - flag for human review on coverage failing (comment, request_reviews)
-
author~=^(pyup-bot|dependabot)$
-
-merged
-
status-failure=test (3.x, 12, py3-cov)
Rule: Dependency updater - flag for human review on lint failing (comment, request_reviews)
-
-status-failure=test (3.x, 12, py3-cov)
-
author~=^(pyup-bot|dependabot)$
-
-merged
-
status-failure=test (3.x, 12, lint)
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