improve logging for settings #52
Merged
Mergify / Summary
succeeded
Jun 4, 2024 in 0s
3 potential rules
Rule: Add CI label (label)
- any of:
-
files~=.github/
-
files~=.markdownlint-config.yaml
-
files~=e2e/
-
files~=tests/
-
files~=tox.ini
-
title~=^ci:
-
title~=^e2e:
-
title~=^tox:
-
Rule: Add Mergify label (label)
- any of:
-
files~=.mergify.yml$
-
title~=^mergify:
-
Rule: Automatic merge on approval (merge)
-
-closed
[📌 merge requirement] -
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] - all of:
-
-draft
-
check-success=e2e (3.10, bootstrap)
-
check-success=e2e (3.11, bootstrap)
-
check-success=e2e (3.11, build_with_build_order)
-
check-success=e2e (3.11, report_missing_dependency)
-
check-success=e2e (3.12, bootstrap)
-
check-success=e2e (3.12, build_with_build_order)
-
check-success=e2e (3.12, report_missing_dependency)
-
check-success=linter
-
check-success=markdownlint
-
check-success=pkglint
-
check-success=unit (3.10)
-
check-success=unit (3.11)
-
check-success=unit (3.12)
- any of:
-
author=dhellmann
-
approved-reviews-by=dhellmann
-
-
- 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!
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