feat(scan): add support for specifying the scan function timeout #1340
Mergify / Summary
succeeded
Dec 6, 2024 in 0s
2 potential rules
Rule: Automatic merge on approval and successful build (delete_head_branch)
-
#approved-reviews-by>=1
-
closed
[📌 delete_head_branch requirement] -
status-success=build
-
status-success=package-js
-
status-success=package-python
-
-label~=(do-not-merge)
Rule: Automatic merge on approval and successful build (queue)
-
#approved-reviews-by>=1
-
status-success=build
-
status-success=package-js
-
status-success=package-python
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection]
-
- all of: [📌 queue conditions of queue
-
-closed
[📌 queue requirement] -
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
-label~=(do-not-merge)
- 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