Rule: Automatic merge (merge)

• author=scalameta-bot
• check-success="'++2.12.12! test' adopt@1.11"
• check-success="'++2.12.12! test' adopt@1.8"
• check-success="'++2.12.18 test' adopt@1.11"
• check-success="'++2.12.18 test' adopt@1.8"
• check-success="'++2.13.12 test' adopt@1.11"
• check-success="'++2.13.12 test' adopt@1.8"
• check-success="'++3.3.0 test' 17"
• check-success="'++3.3.0 test' adopt@1.11"
• check-success="'++3.3.0 test' adopt@1.8"
• check-success="scripted adopt@1.11"
• check-success="scripted adopt@1.8"
• -conflict [:pushpin: merge requirement]
• -draft [:pushpin: merge requirement]
• -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
• check-success="'++2.12.12! test' 17"
• check-success="'++2.12.18 test' 17"
• check-success="'++2.13.12 test' 17"
• check-success=Scalafmt
• check-success=Website
• check-success=Windows
• check-success=scripted 17

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