[2.10.x] Never trigger release process via UI, need to push tag by hand always #958
Mergify / Summary
succeeded
Jan 10, 2024 in 1s
2 rules match and 1 potential rule
Rule: Merge PRs that are ready (queue)
-
#approved-reviews-by>=1
-
label=status:merge-when-green
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
-draft
[📌 queue requirement] -
-mergify-configuration-changed
[📌 queue -> allow_merging_configuration_change setting requirement] -
check-success~=/ Ready To Merge$
-
label!=status:block-merge
- any of: [🔀 queue conditions]
- all of [📌 queue conditions of queue
default
]
- all of [📌 queue conditions of queue
✅ Rule: Delete the PR branch and remove label after merge/close (delete_head_branch)
-
closed
[📌 delete_head_branch requirement] - any of:
-
closed
-
merged
-
✅ Rule: Delete the PR branch and remove label after merge/close (label)
- any of:
-
closed
-
merged
-
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
1 not applicable rule
Rule: Labeling for Scala Steward PR's (label)
-
author=scala-steward
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