Update scalatest from 3.2.19 to 3.2.20 #1483
+1
−1
Merged
Mergify / Summary
succeeded
Mar 27, 2026 in 0s
2 rules match and 2 potential rules
✅ Rule: assign and label scala-steward's PRs (label)
-
author=scala-steward
Rule: merge Scala Steward's PRs (merge)
-
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
author=scala-steward -
base=master -
status-success=build - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = build -
check-neutral = build -
check-skipped = build
-
✅ Rule: automatic merge on CI success and review (delete_head_branch)
-
#approved-reviews-by>=1 -
#changes-requested-reviews-by=0 -
#review-requested=0 -
base=master -
closed[📌 delete_head_branch requirement] -
status-success=build
Rule: automatic merge on CI success and review (merge)
-
-closed[📌 merge requirement] -
#approved-reviews-by>=1 -
#changes-requested-reviews-by=0 -
#review-requested=0 -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
base=master -
status-success=build - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = build -
check-neutral = build -
check-skipped = build
-
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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