chore(deps): update crate-ci/typos action to v1.46.0 #396
Mergify / Summary
succeeded
May 5, 2026 in 1s
1 potential rule
Rule: Automatic merges for Renovate pull requests (merge)
-
-closed[π merge requirement] -
#commits-behind = 0[π‘ GitHub repository ruleset rule{}] -
-conflict[π merge requirement] -
-draft[π merge requirement] -
author~=^renovate\[bot\]$ -
check-success=all-checks - any of: [π merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [π‘ GitHub repository ruleset rule
main]-
check-success = all-checks -
check-neutral = all-checks -
check-skipped = all-checks
-
1 not applicable rule
Rule: Be author's friend (merge)
-
-closed[π merge requirement] -
author~=^ubiratansoares -
#commits-behind = 0[π‘ GitHub repository ruleset rule{}] -
-conflict[π merge requirement] -
-draft[π merge requirement] -
check-success=all-checks - any of: [π merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [π‘ GitHub repository ruleset rule
main]-
check-success = all-checks -
check-neutral = all-checks -
check-skipped = all-checks
-
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