Fix wording in the resolved alerts rule email. #2544
Merged
Mergify / Summary
succeeded
Nov 27, 2024 in 1s
no rules match, no planned actions
💖 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 dependency update on approval (merge)
-
-closed[📌 merge requirement] -
author=dependabot[bot] -
check-success=Community-TC (pull_request) -
label=dependencies -
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
#approved-reviews-by>=1 -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
#review-threads-unresolved = 0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = bugbot tests -
check-neutral = bugbot tests -
check-skipped = bugbot tests
-
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