chore(deps): update dependency semantic-release-preconfigured-conventional-commits to v1.1.59 #548
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Oct 16, 2023 in 1s
1 rule matches and 2 potential rules
Rule: Auto-update with merge if appropriately labeled (update)
-
#commits-behind>0
[:pushpin: update requirement] -
-closed
[:pushpin: update requirement] -
label=auto-update-merge
-
-conflict
-
-draft
Rule: rebase-merge working updates (merge)
-
#commits-behind=0
[🛡 GitHub branch protection] -
#review-threads-unresolved=0
[🛡 GitHub branch protection] -
-conflict
-
-conflict
[:pushpin: merge requirement] -
-draft
-
-draft
[:pushpin: merge requirement] -
-mergify-configuration-changed
[:pushpin: merge -> allow_merging_configuration_change setting requirement] -
label=dependencies
- any of:
-
author=renovate[bot]
-
author=dependabot[bot]
-
- any of: [🛡 GitHub branch protection]
-
check-success=ci-cd / success
-
check-neutral=ci-cd / success
-
check-skipped=ci-cd / success
-
Rule: ask to resolve conflict (comment)
-
conflict
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
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