Update sphinx requirement from <7,>=4.6 to >=7.3.7,<8 #503
Mergify / Summary
succeeded
Aug 1, 2024 in 1s
1 potential rule
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.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
### Rule: default (queue)
-
#approved-reviews-by>=1
-
label=ready-to-merge
-
status-success~=Build docs
-
status-success~=docs/readthedocs.org
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-neutral=docs/readthedocs.org:crate-docs-theme
-
check-skipped=docs/readthedocs.org:crate-docs-theme
-
check-success=docs/readthedocs.org:crate-docs-theme
-
-
#changes-requested-reviews-by=0
[🛡 GitHub branch protection]
-
- all of: [📌 queue conditions of queue
-
-draft
[📌 queue requirement] -
status-success~=Build package
- 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