Add support for async strategies and callbacks #433
+958
−128
Closed
Mergify / Summary
succeeded
Feb 6, 2024 in 1s
1 rule matches and 3 potential rules
Rule: warn on no changelog (comment)
-
-closed -
-files~=^releasenotes/notes/ -
label!=no-changelog
Rule: automatic merge without changelog (queue)
-
#approved-reviews-by>=1 -
label=no-changelog - all of:
-
check-success=test (3.10, py310) -
check-success=test (3.11, py311) -
check-success=test (3.12, pep8) -
check-success=test (3.12, py312) -
check-success=test (3.8, py38) -
check-success=test (3.9, py39)
-
-
-draft[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]- any of: [🛡 GitHub branch protection]
-
check-success=Summary -
check-neutral=Summary -
check-skipped=Summary
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
Rule: automatic merge with changelog (queue)
-
#approved-reviews-by>=1 -
files~=^releasenotes/notes/ - all of:
-
check-success=test (3.10, py310) -
check-success=test (3.11, py311) -
check-success=test (3.12, pep8) -
check-success=test (3.12, py312) -
check-success=test (3.8, py38) -
check-success=test (3.9, py39)
-
-
-draft[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]- any of: [🛡 GitHub branch protection]
-
check-success=Summary -
check-neutral=Summary -
check-skipped=Summary
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
✅ Rule: dismiss reviews (dismiss_reviews)
2 not applicable rules
Rule: automatic merge for jd without changelog (queue)
-
author=jd -
label=no-changelog - all of:
-
check-success=test (3.10, py310) -
check-success=test (3.11, py311) -
check-success=test (3.12, pep8) -
check-success=test (3.12, py312) -
check-success=test (3.8, py38) -
check-success=test (3.9, py39)
-
-
-draft[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]- any of: [🛡 GitHub branch protection]
-
check-success=Summary -
check-neutral=Summary -
check-skipped=Summary
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
Rule: automatic merge for jd with changelog (queue)
-
author=jd -
files~=^releasenotes/notes/ - all of:
-
check-success=test (3.10, py310) -
check-success=test (3.11, py311) -
check-success=test (3.12, pep8) -
check-success=test (3.12, py312) -
check-success=test (3.8, py38) -
check-success=test (3.9, py39)
-
-
-draft[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]- any of: [🛡 GitHub branch protection]
-
check-success=Summary -
check-neutral=Summary -
check-skipped=Summary
-
- any of: [🛡 GitHub branch protection]
- all of: [📌 queue conditions of queue
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