Fix pre-commit error #1291
Merged
Fix pre-commit error #1291
Mergify / Summary
succeeded
Jan 27, 2026 in 1s
3 potential rules
Rule: CI automerge when passing all test (merge)
-
-closed[📌 merge requirement] -
label=ready-to-merge -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
base=master -
check-success=CodeQL -
check-success=docs-build (3.12) -
check-success=macOS-latest (3.12) -
check-success=test-ubuntu (3.10) -
check-success=test-ubuntu (3.11) -
check-success=test-ubuntu (3.12) -
check-success=test-ubuntu (3.13) -
check-success=test-ubuntu (3.9) -
check-success=test-windows (3.12) - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: CI automerge when passing all test (comment, label)
-
label=ready-to-merge -
base=master -
check-success=CodeQL -
check-success=docs-build (3.12) -
check-success=macOS-latest (3.12) -
check-success=test-ubuntu (3.10) -
check-success=test-ubuntu (3.11) -
check-success=test-ubuntu (3.12) -
check-success=test-ubuntu (3.13) -
check-success=test-ubuntu (3.9) -
check-success=test-windows (3.12)
Rule: Information about conflicts pull request (comment, label)
-
conflict
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