Release Subpackages #9024
Merged
Release Subpackages #9024
Mergify / Summary
succeeded
Aug 13, 2024 in 0s
1 potential rule
Rule: Automatic merge for Preparing next version (merge)
-
-closed[📌 merge requirement] -
label = "type/prepare-next-version" -
#commits-behind=0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
author = github-actions[bot] - 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!
1 not applicable rule
Rule: Automatic merge for Dependabot pull requests (merge)
-
#approved-reviews-by >= 1 -
-closed[📌 merge requirement] -
author = dependabot[bot] -
check-success = "ci-app-launch-dev (20.x)" -
check-success = "ci-app-lint (20.x)" -
check-success = "ci-app-test (20.x)" -
check-success = "ci-slackbot-proxy-launch-dev (20.x)" -
check-success = "ci-slackbot-proxy-launch-prod (20.x)" -
check-success = "ci-slackbot-proxy-lint (20.x)" -
check-success = "test-prod-node18 / launch-prod" -
check-success = "test-prod-node20 / launch-prod" -
#commits-behind=0[🛡 GitHub branch protection] -
-conflict[📌 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 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