Add Pekko to supported backends #2157
Merged
Mergify / Summary
succeeded
Apr 26, 2024 in 1s
1 rule matches
✅ Rule: delete head branch after merge (delete_head_branch)
-
closed
[📌 delete_head_branch requirement]
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
6 not applicable rules
Rule: automatic merge for softwaremill-ci pull requests affecting build.sbt (merge)
-
-closed
[📌 merge requirement] -
author=softwaremill-ci
-
check-success=mima
-
files=build.sbt
-
#files=1
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
check-success=ci (2.12, JS)
-
check-success=ci (2.12, JVM)
-
check-success=ci (2.12, Native)
-
check-success=ci (2.13, JS)
-
check-success=ci (2.13, JVM)
-
check-success=ci (2.13, Native)
-
check-success=ci (3, JS)
-
check-success=ci (3, JVM)
-
check-success=ci (3, Native)
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: automatic merge for softwaremill-ci pull requests affecting project plugins.sbt (merge)
-
-closed
[📌 merge requirement] -
author=softwaremill-ci
-
check-success=mima
-
files=project/plugins.sbt
-
#files=1
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
check-success=ci (2.12, JS)
-
check-success=ci (2.12, JVM)
-
check-success=ci (2.12, Native)
-
check-success=ci (2.13, JS)
-
check-success=ci (2.13, JVM)
-
check-success=ci (2.13, Native)
-
check-success=ci (3, JS)
-
check-success=ci (3, JVM)
-
check-success=ci (3, Native)
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: semi-automatic merge for softwaremill-ci pull requests (merge)
-
-closed
[📌 merge requirement] -
author=softwaremill-ci
-
check-success=mima
-
#approved-reviews-by>=1
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
check-success=ci (2.12, JS)
-
check-success=ci (2.12, JVM)
-
check-success=ci (2.12, Native)
-
check-success=ci (2.13, JS)
-
check-success=ci (2.13, JVM)
-
check-success=ci (2.13, Native)
-
check-success=ci (3, JS)
-
check-success=ci (3, JVM)
-
check-success=ci (3, Native)
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: automatic merge for softwaremill-ci pull requests affecting project build.properties (merge)
-
-closed
[📌 merge requirement] -
author=softwaremill-ci
-
check-success=mima
-
files=project/build.properties
-
#files=1
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
check-success=ci (2.12, JS)
-
check-success=ci (2.12, JVM)
-
check-success=ci (2.12, Native)
-
check-success=ci (2.13, JS)
-
check-success=ci (2.13, JVM)
-
check-success=ci (2.13, Native)
-
check-success=ci (3, JS)
-
check-success=ci (3, JVM)
-
check-success=ci (3, Native)
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: automatic merge for softwaremill-ci pull requests affecting .scalafmt.conf (merge)
-
-closed
[📌 merge requirement] -
author=softwaremill-ci
-
check-success=mima
-
files=.scalafmt.conf
-
#files=1
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
check-success=ci (2.12, JS)
-
check-success=ci (2.12, JVM)
-
check-success=ci (2.12, Native)
-
check-success=ci (2.13, JS)
-
check-success=ci (2.13, JVM)
-
check-success=ci (2.13, Native)
-
check-success=ci (3, JS)
-
check-success=ci (3, JVM)
-
check-success=ci (3, Native)
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: add label to scala steward PRs (label)
-
author=softwaremill-ci
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