Update flyway-core to 10.14.0 #307
Merged
Mergify / Summary
succeeded
Jun 9, 2024 in 0s
2 potential rules
Rule: automatic merge for master when CI passes and 1 reviews and not WIP (merge)
-
#approved-reviews-by>=1
-
-closed
[π merge requirement] -
#review-threads-unresolved=0
[π‘ GitHub branch protection] -
-conflict
[π merge requirement] -
-draft
[π merge requirement] -
base=main
-
check-success=build (Scala2_13)
-
check-success=build (Scala3_3)
-
label!=work-in-progress
- any of: [π merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [π‘ GitHub branch protection]
-
check-success=build (Scala2_13)
-
check-neutral=build (Scala2_13)
-
check-skipped=build (Scala2_13)
-
- any of: [π‘ GitHub branch protection]
-
check-success=build (Scala3_3)
-
check-neutral=build (Scala3_3)
-
check-skipped=build (Scala3_3)
-
Rule: automatic merge for master when CI passes and author is steward (merge)
-
-closed
[π merge requirement] -
#review-threads-unresolved=0
[π‘ GitHub branch protection] -
-conflict
[π merge requirement] -
-draft
[π merge requirement] -
author=scala-steward-geirolz[bot]
-
base=main
-
check-success=build (Scala2_13)
-
check-success=build (Scala3_3)
- any of: [π merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [π‘ GitHub branch protection]
-
check-success=build (Scala2_13)
-
check-neutral=build (Scala2_13)
-
check-skipped=build (Scala2_13)
-
- any of: [π‘ GitHub branch protection]
-
check-success=build (Scala3_3)
-
check-neutral=build (Scala3_3)
-
check-skipped=build (Scala3_3)
-
πΒ Β Mergify is proud to provide this service for free to open source projects.
πΒ Β You can help us by becoming a sponsor!
1 not applicable rule
Rule: automatic merge for master when CI passes and author is dependabot (merge)
-
-closed
[π merge requirement] -
author=dependabot[bot]
-
#review-threads-unresolved=0
[π‘ GitHub branch protection] -
-conflict
[π merge requirement] -
-draft
[π merge requirement] -
base=main
-
check-success=build (Scala2_13)
-
check-success=build (Scala3_3)
- any of: [π merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [π‘ GitHub branch protection]
-
check-success=build (Scala2_13)
-
check-neutral=build (Scala2_13)
-
check-skipped=build (Scala2_13)
-
- any of: [π‘ GitHub branch protection]
-
check-success=build (Scala3_3)
-
check-neutral=build (Scala3_3)
-
check-skipped=build (Scala3_3)
-
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