Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

* add a failing test for eachWhere vs closure #47

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

* add a failing test for eachWhere vs closure

045b57a
Select commit
Loading
Failed to load commit list.
Open

* add a failing test for eachWhere vs closure #47

* add a failing test for eachWhere vs closure
045b57a
Select commit
Loading
Failed to load commit list.
This check has been archived and is scheduled for deletion. Learn more about checks retention
Mergify / Summary succeeded Feb 8, 2024 in 1s

1 potential rule

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!

5 not applicable rules

Rule: automatic merge for scala-steward pull requests affecting build.sbt (merge)

  • -conflict [📌 merge requirement]
  • author=softwaremill-ci
  • files=build.sbt
  • status-success=ci
  • #files=1
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: automatic merge for scala-steward pull requests affecting project plugins.sbt (merge)

  • -conflict [📌 merge requirement]
  • author=softwaremill-ci
  • files=project/plugins.sbt
  • status-success=ci
  • #files=1
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: semi-automatic merge for scala-steward pull requests (merge)

  • #approved-reviews-by>=1
  • -conflict [📌 merge requirement]
  • author=softwaremill-ci
  • status-success=ci
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: automatic merge for scala-steward pull requests affecting project build.properties (merge)

  • -conflict [📌 merge requirement]
  • author=softwaremill-ci
  • files=project/build.properties
  • status-success=ci
  • #files=1
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: automatic merge for scala-steward pull requests affecting .scalafmt.conf (merge)

  • -conflict [📌 merge requirement]
  • author=softwaremill-ci
  • files=.scalafmt.conf
  • status-success=ci
  • #files=1
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
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

View more details on Mergify