build(deps-dev): bump org.assertj:assertj-core from 3.11.1 to 3.27.7 #179
Mergify / Summary
succeeded
Jan 26, 2026 in 0s
5 potential rules
Rule: ci testing kalo sukses ke squash dengan label (merge)
-
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
label=ready-to-merge -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
base=main -
check-success=build - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Rule: ci testing kalo sukses ke squash dengan label (comment, label)
-
label=ready-to-merge -
base=main -
check-success=build
Rule: java label (label)
-
files~=\.java$
Rule: markdown label (label)
-
files~=\.md$
Rule: request java team untuk review (request_reviews)
-
label=java files
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