Update sbt-scalafix to 0.13.0 #592
Open
Mergify / Summary
succeeded
Sep 28, 2024 in 1s
1 potential rule
Rule: automatically merge scala-steward's PRs (merge)
-
body~=labels:.*semver-patch
-
status-success=codecov/patch
-
status-success=codecov/project
- any of: [π‘ GitHub branch protection]
-
check-neutral = build (2.12.17, scalaUriJS, coverage, coverageReport)
-
check-skipped = build (2.12.17, scalaUriJS, coverage, coverageReport)
-
check-success = build (2.12.17, scalaUriJS, coverage, coverageReport)
-
- any of: [π‘ GitHub branch protection]
-
check-neutral = build (2.12.17, scalaUriJVM, coverage, coverageReport)
-
check-skipped = build (2.12.17, scalaUriJVM, coverage, coverageReport)
-
check-success = build (2.12.17, scalaUriJVM, coverage, coverageReport)
-
- any of: [π‘ GitHub branch protection]
-
check-neutral = build (2.13.10, scalaUriJVM, coverage, coverageReport)
-
check-skipped = build (2.13.10, scalaUriJVM, coverage, coverageReport)
-
check-success = build (2.13.10, scalaUriJVM, coverage, coverageReport)
-
- any of: [π‘ GitHub branch protection]
-
check-neutral = build (2.13.10, scalaUriJS, coverage, coverageReport)
-
check-skipped = build (2.13.10, scalaUriJS, coverage, coverageReport)
-
check-success = build (2.13.10, scalaUriJS, coverage, coverageReport)
-
- any of: [π‘ GitHub branch protection]
-
check-neutral = build (3.2.2, scalaUriJS)
-
check-skipped = build (3.2.2, scalaUriJS)
-
check-success = build (3.2.2, scalaUriJS)
-
- any of: [π‘ GitHub branch protection]
-
check-neutral = build (3.2.2, scalaUriJVM)
-
check-skipped = build (3.2.2, scalaUriJVM)
-
check-success = build (3.2.2, scalaUriJVM)
-
-
#commits-behind = 0
[π‘ GitHub branch protection] -
-closed
[π merge requirement] -
-conflict
[π merge requirement] -
-draft
[π merge requirement] -
author=scala-steward
- any of: [π merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
πΒ Β 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
Loading