Rule: delete head branch after merge (delete_head_branch)

• closed [:pushpin: delete_head_branch requirement]

Rule: automatic merge for softwaremill-ci pull requests affecting build.sbt (merge)

• #files=1
• -conflict [:pushpin: merge requirement]
• -draft [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• author=softwaremill-ci
• 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)
• check-success=mima
• files=build.sbt

Rule: automatic merge for softwaremill-ci pull requests affecting project plugins.sbt (merge)

• files=project/plugins.sbt
• #files=1
• -conflict [:pushpin: merge requirement]
• -draft [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• author=softwaremill-ci
• 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)
• check-success=mima

Rule: semi-automatic merge for softwaremill-ci pull requests (merge)

• #approved-reviews-by>=1
• -conflict [:pushpin: merge requirement]
• -draft [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• author=softwaremill-ci
• 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)
• check-success=mima

Rule: automatic merge for softwaremill-ci pull requests affecting project build.properties (merge)

• files=project/build.properties
• #files=1
• -conflict [:pushpin: merge requirement]
• -draft [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• author=softwaremill-ci
• 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)
• check-success=mima

Rule: automatic merge for softwaremill-ci pull requests affecting .scalafmt.conf (merge)

• files=.scalafmt.conf
• #files=1
• -conflict [:pushpin: merge requirement]
• -draft [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• author=softwaremill-ci
• 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)
• check-success=mima

Rule: add label to scala steward PRs (label)

• author=softwaremill-ci

---

💖  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